Topic starter
06/07/2026 9:39 am
TL;DR: As AI agents move into systems that hold sensitive data or trigger privileged actions, traditional human-first identity models fracture around authentication, authorisation, and audit, according to Descope. The governance problem is no longer theoretical: agent-native identity standards now determine whether deployments remain governable at scale.
Editorial analysis by NHI Mgmt Group, based on content published by Descope: “Descope Joins the Agentic AI Foundation (AAIF)”.
By the numbers:
- 88% of organisations use or are planning to use AI agents, according to Descope.
- Only 37% have moved past pilots due to identity headaches, according to Descope.
Key questions
Q: What breaks when AI agents use MCP without stronger governance?
A: Governance breaks when the organisation assumes access happens through a stable, inspectable human workflow.
Q: Why do agentic AI deployments become risky when identity controls are coarse-grained?
A: Agentic AI becomes risky because it can act within whatever access it is given, including broad permissions that were never designed for autonomous decision making.
Q: How can organisations tell whether MCP access is actually being governed?
A: A governed MCP deployment can answer who requested access, what scope was granted, when the token expires, and which tool calls were made under that token.
Practitioner guidance
- Define MCP as a governed access surface Classify every MCP-connected system as an identity control point and require explicit policy for which agent identities may invoke which tools and data sources.
- Replace durable agent credentials with task-scoped authorisation Use short-lived grants, constrained scopes, and explicit tool permissions so the agent cannot carry broad standing access across unrelated workflows.
- Require per-action audit evidence Log the agent identity, tool call, target system, decision context, and authorisation outcome for each MCP transaction so reviews can reconstruct what happened.
Bottom line: MCP expands the identity problem from login to governed runtime action, because AI agents can reach multiple systems and trigger privilege-bearing workflows.
Explore further
View Full Forum → | NHI Foundation Course → | Our Services → | Read the full analysis →
06/07/2026 9:54 am
Agentic identity turns MCP into a governance boundary, not just a transport layer. Once an AI agent can reach multiple business systems through a common protocol, identity is no longer confined to login and token issuance. The real question becomes whether the organisation can prove what the agent was allowed to do at the moment it acted. That shifts MCP from an integration topic into an identity governance control point for autonomous execution.
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.
- Only 13% of organisations feel extremely prepared for the reality of agentic AI despite the majority racing toward autonomous adoption, according to the 2026 Infrastructure Identity Survey.
A question worth separating out:
Q: How should teams handle offboarding and privilege changes for AI agents?
A: Treat agent offboarding and scope changes as lifecycle events, not configuration clean-up. If an agent can be retired, re-scoped, or repurposed without revoking old access paths, the organisation is carrying standing exposure. The control objective is to make agent identity changes traceable, revocable, and tied to ownership just like other privileged non-human identities.
👉 Read our full editorial: Agentic AI identity governance needs stronger standards as MCP scales