Notifications
Clear all
Topic starter
22/08/2026 12:01 pm
TL;DR: MCP servers give AI agents a standardized way to discover tools, invoke APIs, and reach enterprise data, but that same layer creates a security blind spot when discovery, policy, and runtime enforcement do not keep pace, according to Trust3. The governance assumption that access can be safely approved once at build time collapses when agents select tools and data paths at runtime.
NHIMG editorial — based on content published by Trust3: What is an MCP Server and Why Is It a Security Blind Spot?
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.
- 53% of MCP servers expose credentials through hard-coded values in configuration files.
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 servers create new visibility gaps for IAM teams?
A: MCP servers create visibility gaps because tool invocation happens inside AI-mediated sessions that span multiple clients and often lack a clean audit trail.
Q: What breaks when AI agents are connected directly to enterprise systems?
A: Direct connections often break auditability, predictable authorisation, and operational containment.
Practitioner guidance
- Inventory every MCP connection and AI agent Create a live register of sanctioned and unsanctioned agents, the MCP servers they touch, and the tools they can invoke.
- Bind access to declared purpose Replace broad role grants with task-scoped policy that evaluates intent per request, then expires access when the task ends.
- Scope credentials per tool and integration Stop reusing shared service accounts across multiple agents or MCP servers.
What's in the full article
Trust3's full article covers the operational detail this post intentionally leaves for the source:
- Step-by-step MCP governance sequence for discovery, policy definition, monitoring, and enforcement across connected agents.
- Examples of how Trust3 maps purpose-based access control to Snowflake, Databricks, and BigQuery request flows.
- Implementation detail on tamper-evident audit trails, kill switches, and runtime guardrails for misbehaving agents.
- A comparison of Trust3, Zenity, Palo Alto Networks, and Immuta from an operational control perspective.
👉 Read Trust3's analysis of MCP server security and agent governance →
MCP server security: are your agent controls keeping up?
Explore further
22/08/2026 12:02 pm
MCP server security is really a governance problem about delegated action, not model output. The article correctly separates what the model says from what the agent does. That distinction matters because access risk now emerges when an identity can call tools, retrieve data, and trigger transactions at runtime. The field needs to stop treating agent security as a content-safety extension of AI governance and start treating it as a privileged execution problem. Practitioners should frame MCP as part of the identity control plane, not as a sidecar to application security.
A few things that frame the scale:
- 92% agree governing AI agents is critical to enterprise security, yet only 44% have implemented any policies to do so, according to AI Agents: The New Attack Surface report.
- While 71% of IT teams have been advised on AI agent data access, only 47% of compliance teams, 39% of legal teams, and 34% of executives have the same visibility, according to AI Agents: The New Attack Surface report.
A question worth separating out:
Q: What should organisations do about shadow AI in MCP environments?
A: Organisations should discover unmanaged agents before expanding gateway policy. If an agent is not registered, no amount of RBAC at the gateway will fully govern it. Discovery, registration, and enforcement need to be part of the same operating process so hidden access paths do not bypass the control plane.
👉 Read our full editorial: MCP server security exposes the blind spot in agent governance
