- Rating
- 2
- Confidence
- 3
- Informativeness
- 2
- Presentation
- 2
- Soundness
- 2
Read review
Paper summary
The paper identifies a structural limitation of action guardrails. When a guardrail makes a decision from a fixed summary of a tool call, it cannot distinguish an action requested by the user from the same action induced by a prompt injection. This limitation arises because the summary does not contain the source of the instruction.
The work establishes model-agnostic limits that can be computed from the summary and a labelled traffic sample alone. These limits include an AUROC ceiling, a floor on attack pass-through at a given benign retention, and the action classes that every such guardrail must allow. A tool is provided to compute these limits. The work also diagnoses how counterfactual certification benchmarks can write labels into provenance fields, which leaves a near-perfect certificate uninformative about deployment.
The validation includes several components. The authors audit their own record-only guardrail and approximations of tool allowlists, static rules, and permission dialogues on the AgentDojo benchmark. The gap comes down to this one missing field: giving LLM judges the instruction's provenance.
Critical strengths
Firstly, the paper introduces a method to analyze why the guardrails fail during deployment and whether the failure lies in what the guardrail sees or in what it has learned. Using only the fields available to a guardrail and a labelled sample, without access to model weights or the training corpus, a deployer can bound the performance of any guardrail operating on that input and identify the actions that it must allow. Retraining on deployment labels then isolates the part of the gap that is caused by the training corpus. Section 4 further separates boundaries that the input cannot express from boundaries that the corpus mislabels. Although the tools are classical, the diagnostic tells a deployer only the result, not the solution.
Secondly, the paper also exposes a flaw in how agent-safety certification sets are built. Guardrails only learn the provenance fields from certification sets, since the label then becomes a function of them. Removing those fields causes the certified performance to disappear. The coverage analysis in Remarks 1 and 2 then explains why even a near-perfect score provides no information about deployment records that the certification set never encountered. This yields cheap checks that apply beyond this paper, which is another strength.
Critical weaknesses
My main concern is that the authors apply the full certificate-to-deployment audit only to their own guardrail, never to one built by others; the external guardrails (Granite Guardian, Qwen3Guard) are evaluated only through their interfaces on boundaries they never claimed. My suggestion is to test on external papers like ToolSafe or TRIAD. As a result, the paper does not give direct evidence for its claims about real guardrails.
Another concern is that the paper's remedy, an attested provenance field, is the core idea of CaMeL, which the paper cites but does not evaluate. The paper doesn't build such a mechanism itself, and it only tests its provenance proxy against attacks that don't know the defense exists. As a result, the paper shows how much provenance would help, but not how to obtain it reliably, which limits its contribution.
Questions for authors
ToolSafe appears to release TS-Guard with its training data; can you try not auditing it end to end?
Which external, ML-certified, call-only guardrail do the Section 3 certificate results apply to?
Could you report the ceiling and floor when CaMeL's attested provenance is used as the record?
Does the provenance proxy survive an adaptive attack that reformats or encodes injected values?