RESEARCH06 OCT 2026 · 09:07 UTC · 6 MIN READ

MCP Protocol Flaws Let Attackers Hijack AI Agent Chains

Researcher Syed Anas Mohiuddin found a fundamental flaw in the Model Context Protocol (MCP) that lets malicious prompts hop between trusted AI agents, a technique he calls "protocol pivoting." Google, JPMorgan Chase, Weaviate, Rapid7, and government agencies in France and the U.S. have all acknowledged related vulnerabilities in the past five months. The exploit works because agents implicitly trust each other without verifying request sources, effectively abandoning zero-trust princip

RESEARCH DESK
MCP Protocol Flaws Let Attackers Hijack AI Agent Chains
Researcher Syed Anas Mohiuddin found a fundamental flaw in the Model Context Protocol (MCP) that lets malicious prompts hop betwee…
MCP Protocol Flaws Let Attackers Hijack AI Agent Chains

Short answer: Researcher Syed Anas Mohiuddin found a fundamental flaw in the Model Context Protocol (MCP) that lets malicious prompts hop between trusted AI agents, a technique he calls "protocol pivoting." Google, JPMorgan Chase, Weaviate, Rapid7, and government agencies in France and the U.S. have all acknowledged related vulnerabilities in the past five months. The exploit works because agents implicitly trust each other without verifying request sources, effectively abandoning zero-trust principles in agentic architectures.

MCP protocol AI agent trust flaw

It turns out there's a fundamental flaw in how AI agents trust each other inside corporate networks, and it centers on the Model Context Protocol. Independent researcher Syed Anas Mohiuddin showed that malicious prompts can hop from one specialized agent to another by exploiting the implicit trust baked into MCP, the communication standard that lets agents delegate tasks without ever verifying the source. In just the last five months, Google, JP Morgan Chase, Weaviate, Rapid7, the French government's interministerial digital directorate, and the U.S. federal government have all acknowledged vulnerabilities tied to this exact mechanism.

Think of the protocol like a hallway where every door is locked but nobody checks who walks between rooms. An attacker plants a crafted prompt in content that a first agent, say, a translation tool, reads and passes along as a normal delegated request. The second agent executes it because it trusts the first agent by design. Each component behaves exactly as intended, which makes the chain incredibly difficult to detect. Douglas McKee, director of vulnerability intelligence at Rapid7, described it perfectly: every protocol checks its own front door while nobody watches the hallway in between.

CVE-2026-97228 vulnerability details

Rapid7's vulnerability, tracked as CVE-2026-97228, carried a modest severity rating of 2.7 out of 10 and was patched last month. Google's flaw was far more serious, rated 8 out of 10. It originated in the googleapis/mcp-toolbox component, which initialized its HTTP client without a CheckRedirect policy and failed to validate target IP addresses. A manipulated path parameter could force the toolbox to follow a redirect to an internal endpoint and issue requests on the attacker's behalf. Google's fix introduced an allow-list of IP ranges, block lists, and a startup-time rejection of unsafe base URLs rather than waiting for the first request. Syed noted that this approach, validating at initialization, is what a real server-side request forgery guard looks like, and it represents more work than most MCP servers have bothered with.

Protocol pivoting attack technique

Syed calls the technique "protocol pivoting" because the exploit crosses protocol boundaries. An initial compromise via MCP can hand off malicious instructions to another agent using Google's Agent-to-Agent protocol or the emerging Agent Network Protocol. Trust and authorization effectively get lost in translation. Markus Vervier, a researcher at X41 D-Sec, argues the better term remains "prompt injection" and that Syed's method is a subclass of indirect prompt injection. The protocol-hopping aspect, he said, isn't strictly required for such attacks to work, though it makes them unexpected and harder to mitigate.

What makes the findings notable is that the same pivoting technique succeeded across five organizations with nothing in common except their use of MCP. The protocol is new, already widespread, and hasn't been sufficiently tested or hardened. In the rush to build sprawling agentic architectures, organizations have abandoned the zero-trust principle, the assumption that any node may be compromised and that sensitive transactions require explicit authorization. McKee emphasized that anything passed from an LLM to a tool should be treated like input from a stranger on the internet, because in a prompt injection scenario that is exactly what it is. The underlying bugs are old friends, injection and server-side request forgery, and the fixes haven't changed in twenty years. Naming the pattern, he added, is what gets defenders and standards bodies to actually design for it.

Agent-based system security recommendations

For teams building or operating agent-based systems, the immediate takeaway is to stop assuming internal agents are trustworthy. Implement allow-lists and block-lists for outbound connections, validate redirects and target addresses at startup rather than on first use, and require explicit authorization for any agent-to-agent action that touches sensitive data or external endpoints. The protocol layer cannot be the only line of defense.

Frequently asked questions

What is the fundamental flaw in the Model Context Protocol (MCP)?

MCP allows AI agents to delegate tasks without verifying the source, creating implicit trust between agents. Malicious prompts can hop from one agent to another because each component trusts the previous one by design, making the attack chain difficult to detect as every agent behaves exactly as intended.

Google, JP Morgan Chase, Weaviate, Rapid7, the French government's interministerial digital directorate, and the U.S. federal government have all acknowledged vulnerabilities tied to the MCP mechanism since late 2025.

What is "protocol pivoting" and how does it differ from standard prompt injection?

Protocol pivoting describes exploits that cross protocol boundaries-an initial MCP compromise hands off malicious instructions to another agent using Google's Agent-to-Agent protocol or the emerging Agent Network Protocol. Researcher Markus Vervier argues this is a subclass of indirect prompt injection, noting the protocol-hopping aspect isn't strictly required but makes attacks unexpected and harder to mitigate.

How did Google fix their critical MCP vulnerability rated 8 out of 10?

Google's flaw in the googleapis/mcp-toolbox component stemmed from an HTTP client initialized without a CheckRedirect policy and missing target IP validation. Their fix introduced an allow-list of IP ranges, block lists, and startup-time rejection of unsafe base URLs rather than waiting for the first request-validating at initialization, which researcher Syed Anas Mohiuddin noted represents a proper server-side request forgery guard.

What immediate steps should teams take to secure agent-based systems using MCP?

Stop assuming internal agents are trustworthy. Implement allow-lists and block-lists for outbound connections, validate redirects and target addresses at startup rather than on first use, and require explicit authorization for any agent-to-agent action touching sensitive data or external endpoints. The protocol layer cannot be the only line of defense.

Source: Ars Technica

Anthropic IPO Raises $81.3 Billion Amid Governance Questions
industry

Anthropic IPO Raises $81.3 Billion Amid Governance Questions

Anthropic completed its IPO on November 19, 2026, raising $81.3 billion-the largest ever, surpassing SpaceX. The AI lab, founded by ex-OpenAI staff prioritizing safety, adopted a Public Benefit Corporation structure with a Long-Term Benefit Trust holding controlling voting rights alongside founders. However, governance experts question the trust’s independence and AI expertise, noting its four trustees lack deep AI backgrounds and a recent trustee joined Anthropic as an executive, rais

Anthropic Goes Public on Nasdaq at $111.50 Per Share
industry

Anthropic Goes Public on Nasdaq at $111.50 Per Share

Anthropic began trading on Nasdaq under ticker ANT on November 19, opening at $111.50 per share, above its $83 IPO price. The debut valued the AI company at roughly $1.5 trillion, the largest public offering on record. Despite reporting an $80.7 billion net loss for the first half of 2026, revenue reached $16.3 billion. Founders retain control through a dual-class structure. CEO Dario Amodei pledged to prioritize AI safety over profit pressure.

Google Rolls Out Computer Use for Mac Gemini
models

Google Rolls Out Computer Use for Mac Gemini

Google has rolled out a computer use feature for its Gemini macOS app, letting the AI assistant operate across local files, desktop programs, and the web to complete multi-step tasks. Available now in English for U.S. users, the system requires per-app consent and displays a live preview of every action. The launch precedes Apple's upcoming macOS 27.3 restrictions on full disk access for AI agents.

Share this post
Report