TL;DR: MCP error messages can be used to steer an agent into passing PII between servers, according to Repello AI. Session design and tool-argument mediation have to cover movement, not just the human-facing summary.
Editorial analysis by NHI Mgmt Group, based on content published by Repello AI: “Multi-Turn MCP Error Hypnosis: How One Server Exfiltrates PII From Another”.
Key questions
Q: Why does PII-aware sanitisation still fail in MCP workflows?
A: Because sanitisation often protects only what the human sees, not what the agent sends through tool arguments.
Q: How can security teams reduce the risk of MCP error-based prompt steering?
A: They should assume recoverable errors can function as active instructions and test whether tools can shape later model behaviour through warning text, retry prompts, or escalation messages.
Q: What breaks when a shared agent gateway allows unvetted MCP servers?
A: A shared gateway turns one poisoned integration into a broad trust problem.
Practitioner guidance
- Segment trusted and untrusted MCP servers Run privileged data sources and third-party tools in separate agent sessions so one server cannot induce the agent to relay data to another.
- Classify tool arguments as sensitive data flows Apply DLP and policy checks to payloads passed into tools, not just to chat output, because exfiltration can occur inside apparently legitimate parameters.
- Review error-channel influence paths Test whether recoverable errors, retry messages, and warnings can change the agent's downstream tool choices or data-sharing behaviour.
Bottom line: MCP error messages can become an active steering channel when an agent treats recoverable failures as instructions instead of mere diagnostics.
Glossary terms: MCP Error Hypnosis, Tool Argument Exfiltration, Workflow Context Boundary, Agentic Confused Deputy
Explore further
View Full Forum → | NHI Foundation Course → | Our Services → | Read the full analysis →
MCP error hypnosis is a trust-boundary failure, not just a prompt-injection trick. The important shift is that the attacker never needed direct server-to-server connectivity, only a shared agent session with one tool that could ask for context and another that could supply it. That means governance has to start with session design, not just with content filtering. Practitioners should treat mixed-trust MCP composition as a control decision, not a convenience setting.
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.
A question worth separating out:
Q: What should organisations monitor when multiple MCP servers are connected to one agent?
A: They should monitor for cross-server data requests, especially when one tool asks for samples, calibration data, or summaries that were sourced from another tool. Those requests are the signal that the agent is bridging trust tiers. If the client cannot explain the data path, it should not be allowed to complete automatically.
👉 Read our full editorial: MCP error hypnosis turns tool errors into a data exfiltration path