TL;DR: Tool poisoning, excessive permissions, cross-server leakage and exfiltration through chained calls are the failure modes Repello AI highlights in MCP server testing. Agent hosts need isolation, logging and scope review so connected servers stay within a live trust perimeter.
Editorial analysis by NHI Mgmt Group, based on content published by Repello AI: “MCP Server Security Testing: How to Find Vulnerabilities in Model Context Protocol Integrations”.
Key questions
Q: Why do MCP servers increase risk when tool permissions are too broad?
A: MCP servers can expand risk because they sit between an AI client and sensitive backends, often with enough reach to query data, trigger workflows, or modify records.
Q: How can security teams spot unsafe MCP server behaviour?
A: Look for servers that request secrets, widen access unexpectedly, or accept tokens that were not clearly approved for the current task.
Q: What breaks when MCP access is managed separately in each AI client?
A: Governance fragments quickly when each client keeps its own access list.
Practitioner guidance
- Review tool descriptions before connection Inspect every advertised tool for hidden instructions, unusual wording and references to data or files outside its stated purpose.
- Constrain the permission surface Document what each tool can read, write, query or transmit, then reject integrations whose parameters are too open-ended for the task.
- Separate trust domains by session Run broad-access MCP servers in a different AI session from untrusted or experimental servers so one toolchain cannot shape another.
Bottom line: MCP servers expand the AI agent attack surface because tool descriptions, parameters and responses can all be abused.
Glossary terms: MCP tool poisoning, Cross-server Attacks, Permission surface, Tool chaining
Explore further
View Full Forum → | NHI Foundation Course → | Our Services → | Read the full analysis →
Tool descriptions are now part of the trust perimeter: MCP turns tool metadata into an operational control surface, not a static reference page. Because the agent reads those descriptions to decide what to do, malicious or careless metadata can reshape behaviour before any downstream system is touched. That means governance has to treat descriptions, prompts and parameter contracts as identity-bearing inputs, not documentation. The practitioner conclusion is simple: if metadata can influence action, it must be governed like access.
A few things that frame the scale:
- A May 2025 Gartner poll of 147 CIOs and IT leaders found that 24% had already deployed AI agents, 50% were experimenting and 17% planned to deploy by the end of 2026.
A question worth separating out:
Q: Should teams isolate trusted and untrusted MCP servers?
A: Yes, when the servers can influence one another through shared context or broad data access. Isolation reduces the chance that a low-trust integration can steer high-trust operations or leak data across toolchains. Separate sessions are especially important when database, file system and network tools coexist in the same agent workflow.
👉 Read our full editorial: MCP server testing exposes tool poisoning and exfiltration risk