Summary

The paper (arXiv 2608.27146) argues that injection risk in tool-augmented agents comes from conflating two runtime roles: inducing actions from observations and authorizing executions. SARA separates them. A context-isolated Action Probe exposes action-inducing semantics in tool outputs and persistently records action-origin provenance across steps, while actual tool calls are authorized only against the user objective and audited evidence from authorized successful executions, under goal, execution-chain and argument-level support constraints. No-History-Promotion prevents historical recurrence from laundering action origins into execution authority. Across AgentDojo and AgentDyn, attack success stays at or below 0.63% in four primary settings with competitive task utility, consistently across agent backbones.

Why it matters
For teams running MCP-heavy agents this is a directly borrowable architecture split: treat tool outputs as untrusted action suggestions, tie authorization to the user's goal plus previously authorized evidence, and never let an action's origin be promoted by repetition. The untrusted-observation problem is exactly what enterprise MCP gateways are being asked to solve today.
Technical details
Architecture context-isolated Action Probe over Observations (exposes action-inducing semantics, records provenance); authorization against user objective + audited evidence with goal / execution-chain / argument-level support; No-History-Promotion across steps
Results ASR <= 0.63% across 4 primary settings on AgentDojo + AgentDyn; task utility competitive; consistent across agent backbones
Relation untrusted tool outputs as commands — same problem class as enterprise MCP gateway enforcement (trend #2)
Code not stated on paper page
Arxiv 2608.27146, submitted 2026-08-27
Tags
agent-securityprompt-injectiontool-callingmcpauthorizationresearch