Topic starter
16/04/2026 8:02 pm
TL;DR: Model Context Protocol can replace one-off scripts and custom connectors in identity security by giving AI a reusable, governed interface to existing workflows, with audit context and temporary tokens preserved, according to Delinea. The operational shift is that interface strategy now matters as much as automation strategy.
Editorial analysis by NHI Mgmt Group, based on content published by Delinea: “AI doesn’t need more connectors. It needs a better interface”.
Key questions
Q: How should identity teams govern AI workflows without creating connector sprawl?
A: Use one mediated interface for repeated identity tasks and make policy enforcement, authentication, and logging part of that interface.
Q: Why do one-off AI integrations create risk in identity security programmes?
A: They create many separate control paths, each with its own testing, maintenance, and logging burden.
Q: What breaks when AI connectors are not tied to identity context?
A: Without identity context, teams can see that an AI tool accessed data but cannot reliably tell who authorised it, which device was used, or whether the connector should still exist.
Practitioner guidance
- Standardise the AI interface layer Define one governed pathway for AI access to identity workflows instead of building a separate connector for each reporting or automation request.
- Keep authentication and policy enforcement at the boundary Require the mediation layer to use the customer’s existing authentication approach, apply policy checks, and log actions with identity context.
- Limit custom integration sprawl Track every script, connector, and agent-specific workflow as control surface area, then retire duplicate paths where one reusable protocol can serve the same need.
Bottom line: Model Context Protocol shifts identity automation from one-off connectors toward a reusable, governed interface.
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
08/10/2026 5:55 pm
Reusable interface design is becoming an identity governance discipline, not an integration preference. Once AI is expected to retrieve data, format outputs, and initiate workflows, the old one-script-per-use-case model becomes a control fragmentation problem. The article points to a shift from bespoke automation to governed reusability, which is exactly where identity programmes need architectural consistency. Practitioners should treat interface strategy as part of identity governance architecture.
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.
A question worth separating out:
Q: Should teams use temporary tokens for AI-driven identity tasks?
A: Yes, when the task is bounded and the interface enforces policy, temporary tokens help preserve least-privilege access and reduce standing exposure. They work best when paired with request validation, identity context, and logging that shows whether a human or AI initiated the action.
👉 Read our full editorial: MCP as a reusable AI interface for identity security workflows