Topic starter
20/08/2026 6:05 pm
TL;DR: TrueFoundry’s comparison of RunLayer and its own platform shows how AI gateway architecture is converging with MCP governance, shadow AI discovery, and runtime guardrails, while still separating model routing from endpoint discovery, according to TruFoundry. The control question is no longer whether to add policy, but where identity, tool access, and audit must sit to govern agents without fragmenting the stack.
Editorial analysis by NHI Mgmt Group, based on content published by TruFoundry: “RunLayer vs TrueFoundry: MCP governance and AI gateway compared”.
Key questions
Q: How should teams govern agent access when both CLI and MCP are available?
A: Govern them separately, because they expose different execution patterns.
Q: Why does tool-level RBAC matter more than model routing for agent governance?
A: Model routing decides which model answers a request, but tool-level RBAC decides what the agent can actually do.
Q: What are the signs that MCP governance is split across too many layers?
A: You usually see duplicated policy logic, inconsistent audit trails, raw credentials in builder workflows, and no clear owner for shadow AI discovery.
Practitioner guidance
- Map the trust boundary for model, tool, and agent access Document which layer owns authentication, authorisation, and audit for models, MCP servers, and agent sessions so the control plane does not fragment across teams.
- Separate discovery from enforcement Treat endpoint inventory of unsanctioned MCP activity as a different control from inline policy checks on approved gateway traffic.
- Define tool-level RBAC for agents Scope each agent to the minimum set of tools it can invoke, and apply approval gates to destructive actions before invocation.
Bottom line: The core issue is not whether AI gateways exist, but whether they own the trust boundary for models, tools, and agents in a way that identity teams can govern.
Explore further
View Full Forum → | NHI Foundation Course → | Our Services → | Read the full analysis →
20/08/2026 6:40 pm
AI gateway governance is now an identity problem, not just a traffic problem: once models, tools, and agents converge in the same control plane, authorisation and audit become as important as routing. The article shows that practitioners are choosing between endpoint discovery and inline governance, but the deeper shift is that trust must now be defined at the tool boundary as well as the model boundary. The implication is that gateway architecture and identity architecture can no longer be designed separately.
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.
- AI-related credential leaks surged 81.5% year-over-year in 2025, with the surrounding AI infrastructure leaking 5x faster than core LLM providers, according to the State of Secrets Sprawl 2026.
A question worth separating out:
Q: Should security teams compare endpoint discovery with inline gateway controls?
A: Yes, because they solve different problems. Endpoint discovery finds unsanctioned MCP servers and agent activity that were never declared, while inline gateway controls govern approved calls after authentication. If a team treats them as substitutes, it will either miss shadow usage or overestimate the reach of its inline policy model.
👉 Read our full editorial: AI gateway governance for MCP and agent access is converging