Topic starter
17/08/2026 5:39 pm
TL;DR: Unosecur says agentic AI and Model Context Protocol are expanding enterprise access faster than teams can govern it, with persistent credentials, weak rotation, and limited auditability now defining the dominant MCP pattern. Static IAM assumptions break when MCP turns non-human identity into a live execution layer, not just a tooling layer.
Editorial analysis by NHI Mgmt Group, based on content published by Unosecur: “Agentic AI Security Challenges and MCP Governance Explained”.
Key questions
Q: How should security teams govern MCP access in agentic workflows?
A: Security teams should govern MCP access as delegated identity, not simple application connectivity.
Q: Why do persistent MCP credentials create such a high-risk access model?
A: Persistent credentials outlive the task that justified them, which means a transient agent can retain durable access to data and tools long after the original intent has changed.
Q: What are the signs that MCP governance is failing?
A: Common signs include agents reaching systems outside their intended workflow, incomplete audit trails for tool use, and data retrieval that cannot be tied back to a clear business purpose.
Practitioner guidance
- Define every MCP server as a governed identity endpoint Inventory MCP clients and servers as first-class identities, including ownership, approved use cases, and access scope, so the governance model covers each trust edge rather than only the underlying application.
- Replace persistent access with task-scoped issuance Use short-lived credentials, explicit session boundaries, and revocation paths so agent access expires with the task instead of lingering as durable secret debt.
- Centralise logging for agent actions and tool calls Capture authentication events, token use, tool invocations, and action outcomes in one audit trail to restore chain of custody across MCP activity.
Bottom line: MCP is creating a new identity security problem because agentic AI uses it as an execution layer, not just a connectivity layer.
What's in the full article
Unosecur's full blog covers the operational detail this post intentionally leaves for the source:
- Step-by-step explanation of the secure MCP Gateway architecture and how it centralises control
- Detailed descriptions of Session & Token Tracking and Policy Manager behaviour across tools
- Practical examples of JIT access and Just Enough Privilege for agent workflows
- The article's own mapping of MCP governance gaps to its identity-centric platform design
👉 Read Unosecur's analysis of agentic AI and MCP governance gaps →
Explore further
View Full Forum → | NHI Foundation Course → | Our Services → | Read the full analysis →
17/08/2026 5:40 pm
MCP governance is now an identity problem before it is an AI problem. The article correctly frames MCP as the connective tissue for agentic AI, but the more important point is that connective tissue becomes control surface. Once clients connect directly to servers with local credentials and no central policy layer, governance fragments across tools instead of being enforced across identities. The implication is that IAM teams must stop treating MCP as a peripheral integration pattern and start treating it as a governed access domain.
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.
- 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.
A question worth separating out:
Q: What happens if teams scale MCP before adding identity controls?
A: The result is usually identity sprawl with little visibility, making every new server and tool connection another trust edge. In that scenario, agentic AI can use legitimate access to discover secrets, move data, or trigger actions that security teams cannot reliably trace or contain.
👉 Read our full editorial: Agentic AI and MCP governance exposes a new identity security gap