Topic starter
02/08/2026 12:14 pm
TL;DR: MCP proxies move governance closer to execution by enforcing policy before an agent reaches a tool or API, according to Akto. Agent identity, tool calls, and approvals need runtime checks when conventional IAM review cycles miss the real risk.
Editorial analysis by NHI Mgmt Group, based on content published by Akto: “MCP Proxy: Security, Observability and Governance of Enterprise AI”.
Key questions
Q: Why do MCP proxies matter for governance and compliance in agentic AI?
A: They create a record of what the agent requested, what the system allowed, and what was blocked.
Q: How can security teams tell whether agent access is actually under control?
A: Look for evidence that the team can trace every tool call, secret use, and cross-system action back to a named owner and a valid approval path.
Q: What breaks when AI agents can call backend tools directly?
A: Direct tool access collapses the boundary between model output and enterprise action.
Practitioner guidance
- Define the MCP proxy as the runtime policy boundary Place all agent-to-tool requests behind a mandatory proxy path so validation happens before execution and direct server access is not possible.
- Map every tool call to an agent identity and context Require request-level identity, role, and purpose data on each interaction so policy decisions are tied to the specific agent action.
- Block unsafe requests before protocol translation Validate prompts and parameters at the proxy layer, then reject requests that attempt sensitive file access, data exfiltration, or unapproved tool use.
Bottom line: MCP proxies move governance closer to execution by enforcing policy before an agent reaches a tool or API.
Glossary terms: MCP proxy, Agentic AI Identity, Identity Blast Radius, Tool-Level Guardrails
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
02/08/2026 1:16 pm
MCP proxy governance is becoming the practical control plane for agentic identity. Once agents can choose tools dynamically, the control point moves from the application boundary to the request path itself. That is a governance shift, not a deployment detail. Security teams should stop treating tool access as a static entitlement problem and start treating it as a runtime enforcement problem.
A few things that frame the scale:
- 67% of organisations still rely heavily on static credentials despite the risks they pose to agentic AI deployments, according to the 2026 Infrastructure Identity Survey.
- Gartner predicts that by the end of 2026, 40% of enterprise apps will feature task-specific AI agents.
A question worth separating out:
Q: What is the difference between agent authentication and MCP proxy enforcement?
A: Authentication answers who the agent is, while proxy enforcement decides what that agent can do with each request. An authenticated agent can still be unsafe if it can reach tools, data, or external services outside policy. The proxy turns identity into actionable control at runtime instead of static access alone.
👉 Read our full editorial: MCP proxy governance defines runtime control for enterprise AI
This post was modified 3 days ago by NHI Mgmt Group