Topic starter
21/08/2026 4:45 pm
TL;DR: Organisations can still miss the decisive access check for AI agents when content security, MCP routing and runtime authorization are collapsed into one gateway, according to Saviynt. Runtime authorization has to sit closer to execution, or agent actions can clear traffic checks without meeting intent or entitlement rules.
Editorial analysis by NHI Mgmt Group, based on content published by Saviynt: “AI Agents Need Three Gateways. Most Enterprises Only Have One.”.
Key questions
Q: Why do AI agents increase authorization risk even when prompts are clean?
A: Clean prompts only tell you that the conversation looks safe.
Q: How do organisations know whether an AI gateway is actually working?
A: Look for three signals at once: AI traffic is inventoried, identity is preserved through the call chain, and audit records are usable in incident response or compliance review.
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 separate control boundaries for each gateway Map content security, tool routing and runtime authorization to different policy owners so no single gateway is treated as complete AI security coverage.
- Bind agent access to task purpose Require policies to evaluate identity, declared intent and action context before execution, not only at connection setup or login.
- Review delegation chains for scope creep Trace how agents inherit and pass permissions across chained tools and sub-agents, then remove assumptions that a valid upstream session implies downstream entitlement.
Bottom line: AI agent security fails when organisations collapse content inspection, routing and authorization into one control plane.
Glossary terms: Runtime Authorisation, MCP Routing, Content Security Gateway, Context-Aware Authorization
Explore further
View Full Forum → | NHI Foundation Course → | Our Services → | Read the full analysis →
This topic was modified 3 days ago by NHI Mgmt Group
21/08/2026 5:05 pm
Three gateway thinking is the right model, but only if teams stop treating connectivity as authorization. Content security, routing and runtime authorization solve different problems, and the failure mode appears when organisations let one layer stand in for another. IAM teams should model the access stack as a sequence of distinct decisions, not a single gateway with broad authority.
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.
- 53% of security leaders expect AI to run major portions of their infrastructure autonomously within the next three years, according to the 2026 Infrastructure Identity Survey.
A question worth separating out:
Q: Should organisations add runtime authorization to existing AI routing controls?
A: Yes, if agents can reach business systems and take actions that have real operational impact. Routing controls manage connectivity, but they do not enforce purpose or entitlement. Runtime authorization becomes necessary when the organisation needs the final decision to happen at the moment of execution.
👉 Read our full editorial: AI agents need three gateways, not one identity control