Topic starter
12/06/2026 9:40 pm
TL;DR: AI agents that reach models and MCP tools create an authorization problem at the gateway: model choice, server visibility, and argument-aware tool calls all need policy enforcement before any upstream request is made, according to Cerbos. The control issue is not just access routing; it is that existing IAM assumptions break when agent requests, model calls, and tool actions converge in one runtime path.
Editorial analysis by NHI Mgmt Group, based on content published by Cerbos: “Governing AI agents at the gateway with Cerbos and agentgateway”.
Key questions
Q: What breaks when an AI gateway does not enforce consistent policy across routes and consumers?
A: When policy is inconsistent, teams lose reliable control over who can access which model, at what quota, and with what data handling rules.
Q: When should teams treat agent gateway decisions as a governance priority?
A: They should treat them as a governance priority whenever the agent can choose a model, enumerate tools, or act on structured arguments without human intervention.
Q: What do organisations get wrong about AI agent authorisation?
A: They often treat agent access as a tooling problem instead of an identity problem.
Practitioner guidance
- Define the gateway as the policy enforcement point Route model traffic and MCP access through a single front door where authorisation is evaluated before any upstream request is made.
- Authorise tool calls on arguments, not just names Inspect structured parameters such as amount, ticket binding, and resource context before permitting an agent to execute a tool action.
- Use fail-closed gateway behaviour Ensure the agent cannot continue when the policy engine is unreachable so access does not degrade into uncontrolled upstream calls.
Bottom line: AI agents create a governance problem at the gateway because model access, MCP visibility, and tool execution converge before downstream controls can intervene.
Explore further
View Full Forum → | NHI Foundation Course → | Our Services → | Read the full analysis →
This topic was modified 7 days ago by NHI Mgmt Group
12/06/2026 11:54 pm
Gateway policy becomes the new identity perimeter for AI agents. Once an agent can reach models and MCP servers from a single runtime path, the old separation between transport control and access control stops being useful. The gateway is where the identity decision now has to happen, because every upstream hop creates a new chance for overreach. Practitioners should treat the gateway as the first and most important enforcement layer for agentic systems.
A few things that frame the scale:
- 19% of organisations give AI systems dramatically more access than human employees, nearly one in five granting unrestricted privilege, according to the 2026 Infrastructure Identity Survey.
- Only 44% of organisations have implemented any policies to manage their AI agents, despite 92% agreeing that governing AI agents is critical to enterprise security, according to the 2026 Infrastructure Identity Survey.
A question worth separating out:
Q: How should IAM teams govern MCP access across SSO, servers, and runtime actions?
A: They should treat MCP access as three separate controls: admission through the IdP, downstream delegation for the server’s own credentials, and runtime authorisation for each tool call. That separation gives each control a clear owner and prevents one valid login from being mistaken for end-to-end safety.
👉 Read our full editorial: Gateway-based authorization for AI agents needs one policy layer
This post was modified 7 days ago by NHI Mgmt Group