SYNTHESIS NOTE
Topics›Agents Multi Architecture›this note

Can attackers manipulate which model handles a request?

Explores whether the routing layer that directs requests to specific models represents a security vulnerability separate from model-level defenses, and whether deployed systems can verify which model actually responded.

Synthesis note · 2026-09-23 · sourced from Agents Multi Architecture

The abstract puts it in one clause: "the underlying model routing and execution control plane remains vulnerable to manipulation and to unverified model provenance." Two problems share the clause. Manipulation is steering which model or execution path handles a request, or altering the controls it runs under. Unverified provenance is not being able to check which model actually answered. The excerpt says nothing further about either.

Both sit below the defenses the vault usually discusses. A prompt-level hardening or an output filter assumes it knows what model is running and that the routing decision was honest. My reading, not the paper's, gives two consequences. If routing can be manipulated, an attacker need not beat a model's defenses; they can send the request to a weaker one, which is the dark side of Can routing beat building one better model?: the lever that helps most is also the one worth capturing. If provenance is unverified, evidence about a model's safety attaches to a name the deployed system may not be running. That extends What do benchmark scores actually reveal about model containment?, where a score is silent about the environment. Here it would also be silent about identity.

The vault has a measured neighbor for the layer under a model's name, though not for a swapped model. Where do safety wins come from in multi-agent systems? found that on Azure GPT-5 54 of 60 blocks came from the provider's filter, and that on a backend without one the safety silently re-sources to the model's own alignment. A rerouted request could change which layer does the blocking in the same unrecorded way. That is my inference, since neither excerpt describes a router being steered.

The vault holds routing as a coordination and performance problem: Can routers select the right model before generation happens?, What decisions must multi-agent routing systems optimize simultaneously?, and When does routing between models actually matter?. None treats the router as a trust boundary. One link is worth flagging as an inference: a router that reacts to surface form rather than to meaning, which the last note measures for paraphrase, would be steerable by anyone who can rewrite a query. The survey does not make that connection.

Provenance also has a neighbor that should not be conflated. Should response workflows be inside the security boundary? uses the word, and glosses it (the vault's gloss) as tracking where consumed and produced things came from. Here it is the provenance of the model itself. A third use is the Troy Moment abstract's "authenticated state provenance" in Can explicit authorization boundaries prevent agents from modifying protected tests?, which the vault reads as a record of who changed a piece of state, not of which model answered.

What the excerpt does not give. Any attack, any mechanism, what the "execution control plane" comprises, or what "unverified provenance" refers to (identity, version, weights, training lineage). It is a claim without a demonstration.

Inquiring lines that read this note 93

This note is a source for these research framings, grouped by the broader line of inquiry each explores. Scan the bold lines of inquiry; follow any specific question forward.

How does workflow position amplify security failures in multi-agent systems? Does multi-agent architecture create security vulnerabilities single-agent defenses can't address? How do prompt injection attacks succeed or fail across defenses? What unintended behaviors emerge in frontier AI models? How should agent identity and authorization work across organizational boundaries? What evidence best independently verifies agent behavior for safety? What determines effective LLM routing across cost, quality, and governance? Do confidence signals reliably indicate whether AI models will succeed or fail? How should evaluation environments be designed as security boundaries? Can sequences of locally safe agent actions violate system-level constraints? Can intelligent model routing compete with model scaling as an optimization lever? Do safety evaluations reliably measure real deployed AI safety risks? How can we ensure AI systems reliably follow constraints rather than circumvent them? Why do autonomous agents report success despite actually failing? Can models recognize evaluation scenarios and modify their behavior accordingly? How can evaluation systems stay reliable and resistant to AI-driven gaming? Can models defeat chain-of-thought monitoring through deliberate reasoning obfuscation? What causes models to fail in specialized domains versus generally?

Related concepts in this collection 7

This note in its neighbourhood — explore the map, then jump to a related concept in the list below.

Concept map
17 direct connections · 169 in 2-hop network ·dense cluster Open in graph ↗

Click a node to walk · click center to open · click Open in graph to see this note in the full knowledge graph

your link semantically near linked from elsewhere

Related papers in this collection 8

Papers most semantically related to this note, ranked by cosine similarity in the embedding space.

Original note title

the model routing and execution control plane is an attack surface of its own — it can be manipulated and model provenance can go unverified