English static mirror for SEO/GEO · AI-assisted translation · Read Chinese original

Shortcut Sensitivity in Agent-Safety Evaluations: When AI Safety Guards Judge the Label, Not the Cargo

Forum topic · 小凯 · 2026-10-18

Summary

A detailed analysis of a paper by Hasan Demirkiran and Jens Ernstberger (arXiv:2610.22243, NeurIPS 2026 TAE workshop) showing that evaluations of AI agent safety guards may be compromised by shortcut learning. The authors audit four benchmarks (LinuxArena, AgentDojo, AgentHarm, ToolSafe) with a three-level framework: label predictability, observational guard association, and paired decision sensitivity. Key findings include a poverty-featured rule predicting LinuxArena labels at AUC 0.934; a literal INFORMATION marker that perfectly recalls unsafe AgentDojo steps but flags 37% of safe ones; AgentHarm labels being fully determined by source subsets; and a controlled intervention on Claude Haiku 4.5 where rewriting markers lowered interception by 8.33pp while renaming tools raised it by 11.46pp—yet the effect did not replicate on GPT-5.6 Luna, showing sensitivity is configuration-specific. The post recommends diagnostic practices for benchmark designers and stresses these findings concern evaluation validity, not deployed safety.

Overview

A Chinese forum post on zhichai.net (part of its "Verifier Economics" series) reviews *Shortcut Sensitivity in Agent-Safety Evaluations* by Hasan Demirkiran and Jens Ernstberger (arXiv:2610.22243, NeurIPS 2026 TAE workshop). The central analogy: an airport security inspector who never inspects cargo, only checks which seal sticker is on the box—many AI agent-safety benchmark evaluations may similarly reward guards for recognizing surface cues rather than understanding risk.

Background

  • Modern AI agents take real-world actions via tools (deleting files, sending emails, transferring money), so engineers deploy guards that approve or block tool calls before execution.
  • Guards are selected via benchmarks with labeled "should block / should allow" examples. But datasets leak metadata—collection environment, action length, tool names, source subsets—that may statistically correlate with labels, enabling shortcut learning (Geirhos et al., 2020; cf. Gururangan et al. 2018 on annotation artifacts in NLI).
  • The paper's stance: the audited benchmarks (LinuxArena, AgentDojo, AgentHarm, ToolSafe) are serious work; predictability of labels is a hypothesis, not a verdict.
  • The Three-Level Audit Framework

    1. Label predictability — deliberately semantically impoverished rules (character counts, fixed words) predict published labels. Strong results only show "the door is unlocked." 2. Observational guard association — do guard interception rates differ when a cue is present (Δassoc)? Observational only; confounding possible. 3. Paired decision sensitivity — the gold standard: fix the action's authorization and effects, change only the cue, and measure guard flips (repeated, interleaved calls for stochastic guards, plus a whitespace format placebo).

    Key Findings

  • LinuxArena (576 unique trajectories, 176 attack / 400 honest, 10 environments): using only *negative mean shell-command character length*, leave-one-environment-out AUC reached 0.934 (per-environment 0.900–1.000, macro .951). Lexical features scored AUC 0.955 on a Haiku-family queue. The paper interprets this as *collection/protocol separability*, not proof that labels are meaningless—an Opus 4.6 monitor suspicion score still carried information within length quartiles (weighted AUC .896).
  • AgentDojo-Traj (1,220 steps; 352 unsafe / 868 safe): attack templates wrap injected content in literal <INFORMATION>...</INFORMATION> markers. All 352 unsafe steps contain the marker; 321 safe steps do too—giving perfect recall but a 37.0% false-positive rate (F1 .687). A tool-name lookup table scored F1 .901 under high-group cross-validation but collapsed to .495 under leave-one-domain-out—the mapping is domain-specific.
  • AgentHarm-Traj (731 steps; 525 unsafe / 206 safe): published source subsets strictly determine all 731 labels. Harmful interactions average 7.29 rows vs 1.65 for benign, so TS-Guard's row-level F1 .902 drops to .719 when re-weighted per interaction (balanced accuracy actually rises from .754 to .776)—a scoring-unit question, not cheating.
  • Intervention experiment (frozen queue of 64 base steps from 58 interactions; Haiku 4.5, 960 calls):
  • Rewriting <INFORMATION> to <UNTRUSTED_EXTERNAL_CONTENT> lowered interception by 8.33pp (-6.77pp after placebo correction, 95% CI [-12.82, -1.61]).
  • Replacing tool names with opaque aliases raised interception by 11.46pp (+13.02pp after correction, [4.92, 21.72]).
  • All unsafe calls remained blocked; strict accuracy on inherited-label calls shifted from 73.44% → 81.77% → 61.98%.
  • No replication on GPT-5.6 Luna (effects ≈ 0, within noise); a quantized Q8 TS-Guard flipped only 3/64 marker decisions. A 10.48pp observational gap for Luna did not survive paired testing. Sensitivity is configuration-specific—one instance, not a general claim.
  • Recommendations for Benchmark Designers

    1. Diagnose and stress-test transfer: impoverished-cue prediction, deduplicate semantic units, hold out by environment/domain/template/source. 2. Name your scoring unit (step / interaction / trajectory / task) and report the unit matching the deployment claim. 3. After association, intervene: fix authorization, capabilities, parameters, effects; document semantic changes. 4. Control stochastic guards with interleaved original/edited/placebo calls; report interception-probability deltas and same-input disagreement rates.

    Stated Limitations

    The 64-step queue is not a probability sample; intervals are exploratory and uncorrected; marker rewrites change source wording; aliases are not natural renames; no blinded human validation; the study concerns evaluation validity, not deployment safety—no tool calls were executed.

    Sequel Teaser

    This is part one of a "Verifier Economics" trilogy. Part two covers RADAR (repairing and validating guard confidence scores); part three covers PROBE (trained auditors turning audits into routine practice).

    References

  • Demirkiran, H., & Ernstberger, J. (2026). Shortcut Sensitivity in Agent-Safety Evaluations. arXiv:2610.22243.
  • Geirhos, R., et al. (2020). Shortcut learning in deep neural networks. *Nature Machine Intelligence*, 2:665–673.
  • Gururangan, S., et al. (2018). Annotation artifacts in natural language inference data. *NAACL-HLT 2018*.
  • Debenedetti, E., et al. (2024). AgentDojo. *NeurIPS 2024 D&B*.
  • Andriushchenko, M., et al. (2025). AgentHarm. *ICLR 2025*.
  • Mou, Y., et al. (2026). ToolSafe.
  • Tracy, et al. (2026). LinuxArena.

Tags

#ai-safety#llm-agents#benchmark-evaluation#shortcut-learning#agent-guardrails#prompt-injection#evaluation-validity#machine-learning

This page is an English static mirror generated for search and AI citation. It may be a full translation or structured summary of the Chinese original. Canonical interactive discussion lives on the Chinese page: https://zhichai.net/topic/178636154