An agent security guard can appear to understand harmful tool behavior while relying on superficial features that correlate with benchmark labels. The Shortcut Sensitivity study tests this possibility by constructing simple predictors from command length and tool names, then changing data splits, names and row weighting without changing the substantive…
Inspect the ClaimsCase · DiggingBeagle record
Agent security monitor benchmarks rewarded command-length and tool-name shortcuts
A study shows high headline monitor F1 can arise from lexical artifacts and per-row weighting without genuine assessment of an operation’s authorization.
arXiv:2610.22243, controlled AgentDojo/AgentHarm/LinuxArena shortcut-sensitivity evaluation.
Assessment profile
Assessment method- Setting
- evaluation
- Exploitation
- not established
- Evidence
- Grade B
- Remediation
- not applicable
- AI role
- AGAINST AI
Basis and provenance
The primary shortcut-sensitivity study publishes feature baselines, changed split assumptions and paired guard tests. These support measurement confounding and selected verdict flips, not live unauthorized side effects against a commercial agent. The evaluated protections and labels do not form a remotely exploitable CVE, so no remediation release applies.
Assessed Oct 18, 2026 using diggingbeagle.assessment/1.
Evidence basis: CLM-CP13-GUARD-LEX · CLM-CP13-GUARD-OOD · CLM-CP13-GUARD-WEIGHT · CLM-ENRICH-GUARD-SPLIT · Shortcut Sensitivity: lexical shortcuts in agent security evaluation
At a glance
Benchmark integrity requires preserving the authorization-relevant action while perturbing incidental labels, names and context. High F1 on random row splits may reward provenance classification instead of determining whether a real tool invocation is allowed. This is conceptually related to LinguaGuard, but language translation and exact tool-name holdout…
Read the implicationsNot a measured in-production guard compromise rate. Some guard populations may maintain effectiveness after shortcut removal and require independent testing.
Limits and uncertaintyFull account
An agent security guard can appear to understand harmful tool behavior while relying on superficial features that correlate with benchmark labels. The Shortcut Sensitivity study tests this possibility by constructing simple predictors from command length and tool names, then changing data splits, names and row weighting without changing the substantive authorization question.
On selected LinuxArena data, command length alone achieved an AUROC around 0.91, and lexical features around 0.934, despite not understanding the requested side effect. A tool-name lookup classifier reached 0.901 F1 on random-fold AgentDojo evaluation but only 0.495 on held-out tool domains. In another example, one AgentHarm guard's F1 changed from 0.902 when rows were weighted individually to 0.719 when entire interactions were weighted. These figures are specific to different experiments and cannot be merged into a general guard failure rate.
The evidence demonstrates shortcut sensitivity and a construct-validity problem, not universal production exploitability. Some tested guards were comparatively resistant to particular changes, and a classifier output is still not proof that a forbidden external action occurred. Evaluation should use unseen tools, interaction-level truth, controlled harmless metadata edits and an independent check of the actual authorized effect.
Claims & evidence
CLM-CP13-GUARD-LEXIn tested LinuxArena data, lexical or command-length features achieved high classification AUROC without causal analysis of a command’s harmful effect.supported
Basis: reported finding
- supportsShortcut Sensitivity: lexical shortcuts in agent security evaluationprimary disclosure
Lexical classifier and command-length controls
CLM-CP13-GUARD-OODA tool-name shortcut classifier scored around 0.901 F1 on random-fold AgentDojo evaluation but 0.495 under unseen-domain split, highlighting overfit.supported
Basis: reported finding
- supportsShortcut Sensitivity: lexical shortcuts in agent security evaluationprimary disclosure
AgentDojo domain-shift experiments and label shortcut tables
CLM-CP13-GUARD-WEIGHTThe study reports substantial changes in aggregate F1 depending on whether AgentHarm is weighted by individual row or full interaction.supported
Basis: reported finding
- supportsShortcut Sensitivity: lexical shortcuts in agent security evaluationprimary disclosure
AgentHarm interaction weighting comparison
CLM-ENRICH-GUARD-SPLITAn exact-tool-name lookup reached F1 0.901 on random folds but 0.495 on held-out tool domains, demonstrating dataset dependence rather than universal guard accuracy.supported
Basis: reported finding
- supportsShortcut Sensitivity: lexical shortcuts in agent security evaluationprimary disclosure
Shortcut sensitivity paper, contributions and domain holdout comparison
Implications
Benchmark integrity requires preserving the authorization-relevant action while perturbing incidental labels, names and context. High F1 on random row splits may reward provenance classification instead of determining whether a real tool invocation is allowed. This is conceptually related to LinguaGuard, but language translation and exact tool-name holdout are distinct perturbations.
Controls and mitigations
- Evaluate guards on held-out tool domains and equal-interaction weighting, with repeated placebo-controlled tests in which the actual requested effect is held fixed.
- Publish both false blocks and missed dangerous effects at the interaction level; do not use one row-weighted F1 score as a standalone permission guarantee.
Unknowns and contradictions
- Not a measured in-production guard compromise rate.
- Some guard populations may maintain effectiveness after shortcut removal and require independent testing.
Sources and citation
Material revision history
- Oct 18, 2026 · Canonical change recorded · new in release · revision 171