Notifications
Clear all
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.
NHIMG editorial — based on content published by Descope: Descope joins the Agentic AI Foundation (AAIF)
By the numbers:
- A recent Descope survey of 400+ identity decision-makers found that while 88% use or are planning to use AI agents, only 37% have moved past pilots due to identity headaches.
Questions worth separating out
Q: How should security teams govern AI agents that connect through MCP?
A: Security teams should govern AI agents through explicit identity, policy, and audit controls at every tool boundary.
Q: Why do traditional IAM controls fail for agentic AI systems?
A: Traditional IAM controls fail because they assume stable identities, predictable workflows, and access that can be reviewed after use.
Q: When should organisations treat an AI agent like a privileged identity?
A: Organisations should treat an AI agent like a privileged identity whenever it can access sensitive data, write to production systems, or chain actions across multiple services.
Practitioner guidance
- Define MCP trust boundaries Map every MCP server and connected tool to a named business owner, an allowed action set, and a logging requirement before the first production rollout.
- Separate agent identity from shared service accounts Issue distinct identities for each agent or agent class so access reviews can trace behaviour to a specific runtime actor instead of a generic integration account.
- Enforce per-action authorisation Require policy checks at each sensitive tool call, especially where agents can write code, modify records, or query regulated data.
What's in the full article
Descope's full post covers the operational detail this post intentionally leaves for the source:
- How Descope's Agentic Identity Hub implements protocol-compliant auth for MCP servers in practice
- What the Python MCP SDK changes for teams embedding authentication and authorisation into agent workflows
- How the company describes enterprise-grade access policy and auditing support for agentic systems
- The survey context behind the move from pilot projects to production governance decisions
👉 Read Descope's analysis of agentic identity governance and MCP access control →
MCP access control for AI agents: what identity teams need now?
Explore further
06/07/2026 9:54 am
Agentic identity is now a governance layer, not a feature flag. Once AI agents can select tools and act across systems, identity stops being a simple authentication problem and becomes a runtime governance problem. Static machine credentials, human-centric approvals, and after-the-fact audit trails do not describe the behaviour that matters. Practitioners should treat agent identity as infrastructure that must be governed from the first production connection.
A few things that frame the scale:
- Only 52% of companies can track and audit the data their AI agents access, leaving 48% with a complete blind spot for compliance and breach investigation, according to AI Agents: The New Attack Surface report.
- 98% of companies plan to deploy even more AI agents within the next 12 months, despite documented rogue behaviour in 80% of current deployments.
A question worth separating out:
Q: What should IAM teams measure to know if agent governance is working?
A: IAM teams should measure whether every agent action can be tied to a specific identity, policy decision, and business purpose. Useful signals include complete audit logs, bounded tool access, and consistent enforcement across connected systems. If actions cannot be reconstructed cleanly, governance is not working even if login succeeded.
👉 Read our full editorial: Agentic AI identity governance needs stronger standards as MCP scales
