Notifications
Clear all
Topic starter
18/08/2026 2:14 pm
TL;DR: Model Context Protocol standardises how AI applications connect to enterprise tools, but BigID’s analysis shows that the protocol also creates a new security boundary where excessive permissions, prompt injection, token misuse, and malicious servers can turn agent actions into real business risk. Treating MCP as part of identity, data, and AI governance is now essential.
NHIMG editorial — based on content published by BigID: Model Context Protocol security and enterprise AI connectivity
Questions worth separating out
Q: How should security teams govern AI agents that can access enterprise systems?
A: Security teams should govern AI agents as non-human identities with explicit ownership, scoped privileges, and continuous monitoring.
Q: Why do chained MCP workflows create extra identity risk?
A: Chained workflows multiply trust boundaries because each MCP server may forward the request to another server.
Q: What do organisations get wrong about MCP security?
A: They often focus on network isolation or prompt filtering and miss the real issue: an authorised workload can still perform an unintended action.
Practitioner guidance
- Map every MCP-connected non-human identity Inventory hosts, clients, servers, tools, prompts, credentials, and data sources as separately governed assets.
- Eliminate token passthrough across MCP workflows Require audience-bound tokens for each downstream service and block any design that forwards a bearer token unchanged.
- Treat retrieved context as untrusted input Validate provenance for resources, server responses, and tool metadata before the model can act on them.
What's in the full article
BigID's full article covers the operational detail this post intentionally leaves for the source:
- A breakdown of MCP host, client, and server responsibilities in enterprise deployments.
- Specific mitigation patterns for prompt injection, tool poisoning, and token passthrough.
- Guidance on governed access, role-based controls, and data policy enforcement for AI workflows.
- Examples of how BigID applies its data governance controls to MCP-enabled use cases.
👉 Read BigID's analysis of MCP security and enterprise AI connectivity →
MCP security and AI connectors: what are teams missing?
Explore further
18/08/2026 3:05 pm
Standardised AI connectivity creates governance debt if identity controls lag behind protocol adoption. MCP reduces integration friction, but it also multiplies the number of entities that can act on enterprise data. That means hosts, clients, servers, prompts, tools, and tokens all need explicit ownership and policy boundaries. For identity teams, MCP is not just an AI integration pattern, it is a new class of non-human identity estate that must be managed like production access.
A question worth separating out:
Q: Who should approve high-risk actions in agentic workflows?
A: The approval model should be tied to the action, not to the existence of the agent. High-risk, destructive, or cross-environment actions need explicit human approval before execution, even when the surrounding workflow is automated. That keeps delegated authority from becoming unchecked execution authority.
👉 Read our full editorial: MCP security turns AI connectors into a new enterprise control plane
