Topic starter
12/06/2026 9:14 pm
TL;DR: MCP is moving agent actions into internal systems, and the current security model was not built for that shift, according to Pomerium’s discussion with RedMonk analysts. Real-time, request-level authorization is now the control point that determines whether human, service, and agent identities can be governed safely.
Editorial analysis by NHI Mgmt Group, based on content published by Pomerium: “What We Heard From RedMonk Analysts—And Why Agentic Access Needs a New Security Model”.
Key questions
Q: What breaks when MCP relies on sessions instead of request-level authorization?
A: Session-based authentication breaks because MCP requests can be generated dynamically by nonhuman identities and routed through tools or intermediaries that were never part of the original trust decision.
Q: Why does MCP increase the importance of runtime authorisation for agentic AI?
A: MCP increases the importance of runtime authorisation because it turns tool use into a dynamic, session-based decision path.
Q: What are the signs that MCP-based agent access is not being governed effectively?
A: Poor governance usually shows up as unclear permissions, inconsistent tool approvals, and weak auditability across agent actions.
Practitioner guidance
- Implement per-request authorization for MCP paths Check every agent-initiated action against policy before it reaches the target system, rather than inheriting trust from the login session.
- Separate human, service and agent identities Assign distinct identity treatment to each actor type so the policy engine can evaluate who initiated the request and what privileges apply.
- Limit agent access to narrow action scopes Constrain what MCP-connected agents can read, write or invoke, and remove broad permissions that are acceptable only for human workflows.
Bottom line: MCP pushes identity governance from session trust toward per-request control because agents can now act inside internal systems.
Explore further
View Full Forum → | NHI Foundation Course → | Our Services → | Read the full analysis →
This topic was modified 2 days ago by NHI Mgmt Group
12/06/2026 11:10 pm
Request-level authorisation is the new control boundary for MCP. Once models can trigger internal actions, the old distinction between login and access decision stops being sufficient. The practical governance shift is that authorisation must happen at the moment of each request, with enough context to evaluate identity, action and target system together.
A question worth separating out:
Q: How should teams govern agent access when both CLI and MCP are available?
A: Govern them separately, because they expose different execution patterns. CLI is usually easier to inventory, validate, and retire, while MCP can preserve state across multiple actions and therefore needs tighter session controls. Access reviews should include interface type, exposed tools, and how state is retained or discarded.
👉 Read our full editorial: Agentic access needs a new security model for MCP requests
This post was modified 2 days ago by NHI Mgmt Group