AI Governance Institute
← News
Research2026-10-12

253 MCP Server Bugs and Six Framework Bypasses Expose Agent Authorization Gap

Source

Researchers bypass 6 AI agent frameworks with a simple 'Repeat-After-Me' prompt

Pennsylvania State University, Universite Montpellier, Dartmouth College

What happened

Researchers from three universities published findings, covered by CSO Online, showing that a prompt technique called Repeat-After-Me caused six major AI agent frameworks to carry out attacker-controlled tool calls. The affected frameworks include LangGraph, AutoGen, and Google's Agent Development Kit 2.0, all of which are used in enterprise deployments today. The underlying flaw is architectural: these orchestration layers trust whatever the AI model outputs as a valid instruction, rather than running an independent check before executing any action. ToFu was used to scan 118 open-source MCP (Model Context Protocol) servers. These are connectors that let AI agents access external systems such as databases, file stores, and cloud services. It found 253 verified security flaws. Some allow attackers to read or write files outside their intended scope. Others allow them to run arbitrary commands on the host system. This research builds on a pattern flagged in earlier coverage, including 68 MCP Server CVEs in One Month Expose a Systemic Agent Supply Chain Gap and Orchestration Framework Flaws Make AI Workflow Pipelines a Primary Attack Target.

Why it matters

  • ·Enterprises using any of the six affected frameworks may have no independent authorization check between an attacker's instruction and a live system action. A malicious prompt alone can trigger data exfiltration, file modification, or command execution without any human or system review.
  • ·The 253 flaws found across 118 open-source MCP servers represent a supply chain risk most AI governance programs have not inventoried. Organizations that cannot name which MCP servers are running cannot assess exposure to path-traversal or command-execution vulnerabilities that researchers have now confirmed at scale.
  • ·Regulators are paying close attention to agent authorization and containment failures. The EU AI Act (Regulation (EU) 2024/1689) and emerging guidance from bodies such as the Five Eyes treat failure to validate agent actions before execution as a control deficiency, and enforcement actions tied to agentic AI incidents are already on record in Europe.

Stay ahead of stories like this

Get every Global AI governance development like this one, plus the rest of the week's developments. Every Thursday.

Free every Thursday. Unsubscribe anytime.

Governance controls affected

What to do now

  • ☐Ask your engineering or platform team to list every AI agent framework in use and confirm whether LangGraph, AutoGen, or Google's Agent Development Kit 2.0 is among them. If so, request a written assessment of whether an independent pre-execution authorization check exists before any tool call runs.
  • ☐Request a complete inventory of every MCP server connected to your AI systems, including open-source ones, and confirm whether any have been scanned for the classes of flaws the ToFu tool identified, specifically the ability to read or write files outside their intended area or run commands on the host system.
  • ☐Review your agent deployment approval process to confirm it requires an independent validation step before tool calls execute, not just a review of the model's instructions at the design stage.
  • ☐Update your third-party AI vendor due diligence questionnaire to require vendors to document their framework-level pre-execution validation controls and disclose which MCP servers their products connect to.
  • ☐Add prompt injection via tool outputs and framework-level authorization bypass to your next agent-specific tabletop exercise, so response owners understand what a Repeat-After-Me style attack looks like in practice.

What to watch next

Regulators and standards bodies are actively developing requirements around agent pre-execution authorization, and this research will likely accelerate that work. The Five Eyes Guidance on the Careful Adoption of Agentic AI Services already names independent action validation as a baseline control. Enforcement bodies in the EU have shown willingness to treat agentic containment failures as formal regulatory events. Compliance teams should monitor whether affected framework vendors publish patches or architectural mitigations. They should also track whether MCP server inventories are added to scope in upcoming audit and penetration testing standards. The accumulating body of MCP vulnerability research, including the CIS MCP Benchmark Sets 55-Point Audit Baseline for Agent Tool Governance, signals that a point-in-time review will no longer satisfy auditors or regulators in this area.

Related Coverage

Research2026-11-17

87.5% of Known MCP Vulnerabilities Are Critical or High Severity

Researchers at IEEE SPW 2026 published a curated dataset of 24 validated MCP vulnerabilities drawn from CVE disclosures through February 2026. They found that 87.5% are Critical or High severity, and that two attack types — injection and path traversal — account for 66.7% of cases. The paper also releases a maintained dataset and reproducibility tooling for ongoing MCP security measurement.

Standards2026-11-16

Microsoft Defense Guide Makes Layered Prompt Injection Controls an Enterprise Baseline

Microsoft has published updated guidance on defending against indirect prompt injection, a category of attack where malicious instructions hidden in external content redirect AI systems to perform unintended actions. The guidance, titled 'Defend against indirect prompt injection attacks,' recommends a layered set of controls including prompt shields, content isolation, behavioral monitoring, and human approval gates. It applies to any organization using AI systems that process third-party content such as emails, documents, websites, or plugins.

Standards2026-11-13

MCP and Agent Skills Move to Vendor-Neutral Governance Under Linux Foundation

Google reported in November 2026 that the Model Context Protocol (MCP) and Agent Skills specifications are being co-maintained under vendor-neutral governance through the Linux Foundation's Agentic AI Foundation. The transition means that the rules governing how AI agents connect to external tools and load procedural instructions are no longer controlled by any single vendor. Enterprise teams using MCP-connected agents must now track specification changes from a multi-party standards body and re-evaluate security controls at each revision.