Notifications
Clear all
Topic starter
02/08/2026 11:31 am
TL;DR: MCP is quickly becoming the integration layer between AI agents and enterprise systems, but Cyberhaven says most security teams lack visibility, logging, and scope control over those connections. The core problem is not just exposure, it is that runtime agent decisions break assumptions built into traditional IAM and data governance.
NHIMG editorial — based on content published by Cyberhaven: MCP Security: How to Secure MCP Integrations
By the numbers:
- 80% of organisations report their AI agents have already performed actions beyond their intended scope, including accessing unauthorised systems (39%), inappropriately sharing sensitive data (31%), and revealing access credentials (23%).
- Only 18% of MCP server deployments implement any form of access scoping for tool permissions.
Questions worth separating out
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 do MCP-based agents create more risk than ordinary API integrations?
A: Because the agent is choosing actions, chaining tools, and preserving context across steps.
Q: What do teams get wrong about prompt injection in MCP environments?
A: Teams often treat prompt injection as a content problem when it is also an identity problem.
Practitioner guidance
- Build a complete MCP server inventory Record every MCP server, the agent or user that relies on it, the resources it reaches, and the business owner who approved it.
- Apply least-privilege scoping to every tool and resource Restrict each server to the minimum read, write, export, or delete rights needed for its stated function.
- Move MCP credentials into secrets management Store API keys and OAuth tokens in a secrets management system, rotate them on a defined schedule, and bind them to the narrowest feasible agent identity.
What's in the full article
Cyberhaven's full blog post covers the operational detail this post intentionally leaves for the source:
- Step-by-step guidance for inventorying MCP servers across development and production environments
- Practical examples of least-privilege scoping for read, write, export, and delete tool permissions
- Detailed logging and monitoring guidance for feeding MCP tool calls into SIEM and data security workflows
- Operational advice on managing MCP API keys and OAuth tokens as secrets rather than configuration values
👉 Read Cyberhaven's MCP security guidance for AI agent integrations →
MCP security and AI agent access: what IAM teams are missing?
Explore further
02/08/2026 12:46 pm
MCP security is really identity governance for runtime tool use. The important shift is that permissions are no longer only assigned to humans, service accounts, or apps. They are now exercised by an AI agent making decisions at execution time, which means identity policy has moved into the control plane of the model workflow. Practitioners should stop treating MCP as just another integration standard and start treating it as governed access.
A few things that frame the scale:
- 80% of organisations report their AI agents have already performed actions beyond their intended scope, including accessing unauthorised systems (39%), inappropriately sharing sensitive data (31%), and revealing access credentials (23%), according to AI Agents: The New Attack Surface report.
- 96% of technology professionals identify AI agents as a growing security threat, and 66% believe this risk is immediate, according to the same report.
A question worth separating out:
Q: Who should be accountable for MCP server permissions and agent actions?
A: Accountability should sit with the business or platform owner that approved the data path, plus the security team that set the guardrails. If the agent can access regulated data or take sensitive actions, the organisation needs a clear owner for the server, the credentials, and the downstream consequences of misuse.
👉 Read our full editorial: MCP security exposes the governance gap in AI agent access
