Topic starter
06/11/2026 6:39 pm
TL;DR: Enterprise MCP adoption is concentrating around Slack, Google Workspace, Snowflake, Datadog, GitHub, Notion and Granola, according to Aizome's analysis of Runlayer usage data, creating persistent trust relationships that most identity and security stacks cannot see. The governing assumption breaks when session-level tool use outruns review-based controls.
Editorial analysis by NHI Mgmt Group, based on content published by Aizome: “MCP Security: What the Most Popular Enterprise MCP Integrations Actually Mean for Your Governance Program”.
By the numbers:
- Every MCP connection in the top 10 shares persistent trust, broad data access and action capability, creating a governance surface that traditional controls do not evaluate in-session.
Key questions
Q: How should teams govern AI agents that use MCP?
A: Treat each connected agent as a non-human identity with an owner, a scope, and a review cycle.
Q: Why is persistent session access risky for AI agents?
A: Persistent session access is risky for AI agents because a long-lived login or token lets the agent keep acting after the original task, approval or supervision has ended.
Q: How do collaboration tool integrations expand an agent's blast radius?
A: Collaboration tool integrations expand an agent's blast radius by giving it access to chats, files, calendars, tickets and shared workspaces through multiple API scopes or delegated tokens.
Practitioner guidance
- Define organisational intent for each MCP connection Record which systems, data types and action classes each agent is allowed to use before the connection goes live.
- Enforce runtime checks on tool calls Evaluate each MCP action against the declared purpose of the agent before the call completes, not after an audit review.
- Inventory shadow MCP integrations Find and classify every agent-to-system connection, including developer-built and user-built integrations that never entered formal review.
Bottom line: MCP creates a governance surface because one authenticated agent session can keep calling tools without fresh behavioural review.
Explore further
View Full Forum → | NHI Foundation Course → | Our Services → | Read the full analysis →
06/11/2026 6:42 pm
Persistent trust is the real MCP governance problem: these integrations turn a single authentication event into an ongoing authority relationship. That breaks the assumption that access can be evaluated at sign-in and then trusted until the next review cycle. The implication is that governance has to move from session issuance alone to session behaviour, because the risky part happens after the login event.
A few things that frame the scale:
- 69% of security leaders agree identity management must fundamentally shift to address agentic AI systems, according to the 2026 Infrastructure Identity Survey.
A question worth separating out:
Q: What should security teams do first when AI agents have too many integrations?
A: First, discover every agent-to-system connection and map each one to the agent, the human owner, the credential used, and the exact scopes granted. That inventory shows which integrations are unnecessary, over-privileged or duplicated, so teams can remove unused connectors, narrow OAuth scopes, rotate tokens and revoke any session that cannot be justified.
👉 Read our full editorial: Most popular MCP integrations expose a hidden governance surface