TL;DR: Connected Model Context Protocol servers expand an agent’s trust boundary by creating a path for instruction injection, scope abuse, credential theft, and data exfiltration, according to ClawSecure. Agents need review and monitoring after approval so delegated access stays within the boundary that was approved.
Editorial analysis by NHI Mgmt Group, based on content published by ClawSecure: “What Is MCP Security? Model Context Protocol Explained”.
Key questions
Q: Why does MCP security need runtime monitoring as well as approval checks?
A: Because approval only validates the server at one moment in time.
Q: How should security teams govern third-party servers that agents can call?
A: They should govern them as delegated access relationships, not as ordinary integrations.
Q: What breaks when a third-party MCP server is installed without pre-install review?
A: The trust model breaks first.
Practitioner guidance
- Audit every connected MCP server before approval Review tool definitions, declared scopes, dependencies, and known malicious patterns before any server is connected to an agent.
- Limit the agent reach each server inherits Constrain filesystem, shell, and network access so a connected server cannot inherit more operational reach than its task requires.
- Monitor runtime behaviour against the approved baseline Watch for unexpected tool calls, scope expansion, unusual data movement, and behaviour that diverges from the original review.
Bottom line: MCP security exists because connected servers can influence an agent’s context, scopes, and next actions, which turns a tooling choice into a trust decision.
Glossary terms: Model Context Protocol, Indirect Prompt Injection, Tool Poisoning, Delegated Access
Explore further
View Full Forum → | NHI Foundation Course → | Our Services → | Read the full analysis →
Third-party MCP access is an identity problem, not just an integration problem: Once an MCP server sits inside the agent’s trust boundary, it becomes part of the identity control plane whether teams model it that way or not. The relevant question is no longer only whether the server is reachable, but whether it is allowed to influence agent decisions, scopes, and downstream actions. That makes governance, not connectivity, the primary control dimension.
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.
- 92% of organisations expose NHIs to third parties, raising concerns about supply chain security, according to the Ultimate Guide to NHIs.
A question worth separating out:
Q: What is the difference between API security and MCP security?
A: API security focuses on protecting known endpoints and request boundaries. MCP security must also govern the agent’s state, the context it carries, and the sequence of tool actions it can trigger. In practice, that means moving from endpoint-centric controls to workflow-centric access policy and continuous enforcement.
👉 Read our full editorial: Mcp security shifts trust into third-party servers and agent access