TL;DR: Nexis says its session shows how MCP can connect AI assistants to identity and authorization data so natural-language questions become tool calls for employees, roles, accounts, permissions and governance context. Identity teams need to constrain tool scope, logging and output boundaries before AI-driven access is enabled.
Editorial analysis by NHI Mgmt Group, based on content published by Nexis: “Talking to Your Identity Platform: MCP, AI Assistants and NEXIS in Practice”.
Key questions
Q: Why can conversational access to roles and permissions create new risk?
A: Because an assistant can reconstruct sensitive privilege relationships faster than a human reviewer and can combine separate answers into a broader picture of the environment.
Q: How should security teams govern MCP gateway identity controls?
A: Treat the gateway as a relay point, not the place where every identity decision lives.
Practitioner guidance
- Define tool-level authorization boundaries Limit which identity objects each MCP tool can read, and separate employee, role, account, permission and governance queries into distinct scopes.
- Treat the assistant as a governed runtime client Require logging, request attribution and read-only defaults for every conversational query against identity data.
- Review compound-query risk Test whether two or three harmless-looking prompts can be combined to expose a privileged view that no single report should reveal.
Bottom line: MCP introduces a new runtime access layer over identity data, so the security problem is governed tool use rather than conversational convenience.
Glossary terms: Model Context Protocol, Delegated Authorization, Identity Blast Radius, Tool Scope
What to expect at the briefing
Nexis's full event briefing covers the operational detail this post intentionally leaves for the source:
- Live demonstration of natural-language questions translated into MCP tool calls against an identity platform
- Real implementation context from FI-TS showing which identity objects were exposed through the workflow
- Practical view of how employees, roles, accounts, permissions and target systems were surfaced
- Speaker discussion of how the session was structured around governance information and access context
👉 Register for Nexis's live briefing on MCP, AI assistants and identity platform access →
Explore further
View Full Forum → | NHI Foundation Course → | Our Services → | Read the full analysis →
MCP changes the control point, not the identity problem: the platform still governs entitlements, but the assistant becomes a new runtime actor that can ask for them in ways humans do not. That means the security issue shifts from static access review to tool invocation governance. If the MCP layer is not separately constrained, identity data becomes machine-readable at a pace and granularity that legacy reporting workflows were never designed to handle. Practitioners should treat the tool layer as part of the identity plane, not an accessory to it.
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.
- 19% of organisations give AI systems dramatically more access than human employees, nearly one in five granting unrestricted privilege, according to the 2026 Infrastructure Identity Survey.
A question worth separating out:
Q: What is the difference between an MCP tool and a standard IAM report?
A: A report is a predefined output, while an MCP tool is an interactive runtime path that can be invoked repeatedly, combined with other tools and shaped by the assistant’s prompt. That makes the tool path more flexible, but also more sensitive to scope and authorization errors.
👉 Read our full editorial: MCP for identity platforms: what natural-language access queries change