Join our Newsletter — 33% off our NHI Course

What would it take for Cloudflare Gateway to govern agents?

 

(@nhi-mgmt-group)
Member Moderator
Joined: 2 years ago
Posts: 20225
Topic starter  

TL;DR: Cloudflare AI Gateway covers caching, rate limits, failover, and token logging, Archestra argues, but not the caller, tool use, or MCP server behind an agent request. Agent governance depends on identity and action policy, not just transport controls.

Editorial analysis by NHI Mgmt Group, based on content published by Archestra: “Cloudflare AI Gateway + Archestra”.

Key questions

Q: Why do agent systems need a different authorisation model than chat apps?

A: Chat apps usually need request-level protection, while agent systems need action-level protection because the runtime can choose tools and sequence work on behalf of a user.

Q: How do security teams know if agent governance is actually working?

A: It is working only if the team can answer three questions quickly for any agent: what it can reach, what it did recently, and whether that behaviour matches intent.

Q: What breaks when AI gateways are treated as the source of trust for agents?

A: Trust collapses because gateways can inspect traffic, but they cannot prove who the agent is, who authorized it, or whether the action is permitted at that moment.

Practitioner guidance

  • Define the edge boundary precisely Use the gateway for caching, rate limits, failover, and provider routing, but do not treat it as the control point for agent actions or tool authorisation.
  • Bind agent actions to a real user identity Require the runtime to resolve the signed-in user before model calls and tool calls, then record that identity in the audit trail.
  • Separate tool access from model access Put policy around which tools an agent can invoke, which MCP servers it can reach, and which actions require per-user delegation.

Bottom line: The central issue is not whether an AI gateway works, but whether it can govern delegated action once an agent starts using tools.

Glossary terms: Agent Layer, Edge Gateway, MCP Gateway, Delegated Authorization

Explore further

View Full Forum →  |  NHI Foundation Course →  |  Our Services →  |  Read the full analysis →


This topic was modified 1 week ago by NHI Mgmt Group

   
Quote
(@mr-nhi)
Member Moderator
Joined: 6 months ago
Posts: 20715
 

Edge controls and agent controls are not the same governance problem. Cloud AI gateways answer questions about cost, latency, caching, and provider failover. Agent runtimes answer questions about delegated authority, tool choice, and who is acting on whose behalf. When teams collapse those into one layer, they create a false sense of coverage that leaves tool access and decision traceability outside the control model.

A few things that frame the scale:

  • 24,008 unique secrets were exposed in MCP configuration files in 2025 alone, the protocol's first year of widespread adoption, according to the State of Secrets Sprawl 2026.

A question worth separating out:

Q: Should teams stack an agent layer above an AI gateway or replace the gateway entirely?

A: Replace neither by default. Use the gateway for provider-side optimisation and use the agent layer for identity-aware tool control, then combine them when the workload has both needs. The right answer depends on whether the risk is model traffic, delegated action, or both.

👉 Read our full editorial: Cloudflare AI Gateway stops at the edge, not the agent layer


This post was modified 1 week ago by NHI Mgmt Group

   
ReplyQuote
Share:

Free weekly newsletter

Subscribe to the NHI & AI Identity Journal

The latest on NHI and Agentic AI security – articles, research, breaches, news and events every week.

Bonus 33% off our NHI Course when you subscribe.