Skip to content
Preprint

The Guard That Cried Wolf: How Scary Words Make Agent Guardrails Refuse Legitimate Actions

Aug 2026 · 0 citations · 26 references
Computer Science

TL;DR

Cautious Bench is constructed, the first benchmark to make over-safety the construct for agent guardrails; it codesigns each sample and its label with a stated authorization policy, and finds a name-superstition effect: each over-refuses an authorized action more often under a scary-looking object name than a benign one.

Abstract

Agent guardrails are checks that approve or refuse each action before an LLM executes it. Sometimes they refuse requests that are genuinely safe. This over-safety blocks deployment when a guardrail refuses an authorized task. Evaluating over-safety is hard: at the boundary an authorized action resembles an unauthorized one, and the safe-versus-unsafe label is a choice of authorization policy, not fixed by the action alone. We argue it therefore requires a benchmark that does not yet exist, one that maps the decision boundary of an ideal guardrail. Harvesting such a benchmark from real data is impractical: boundary cases are hard to collect, their labels hard to verify. The gap is real, so we construct Cautious Bench, the first benchmark to make over-safety the construct for agent guardrails; it codesigns each sample and its label with a stated authorization policy. A build-time gate re-derives every example to certify it, so each label is a mechanical consequence of the policy rather than an annotator's per-sample verdict, a reference against which researchers can measure real guardrails. The benchmark renders 756 Decidable benign/twin pairs, each under three object-name types (2,268 measured pairs), and 40 Undecidable pairs reported separately. Measuring six guardrails from five designs, we find a name-superstition effect: each over-refuses an authorized action more often under a scary-looking object name than a benign one. Since only the object name varies in the aforementioned contrast experiments, the deviation is the name's doing: the guardrails read the surface label, not the authorization context.

View source

Similar papers

#artificial intelligence Review Oct 2026

Not Self-Decidable: LLMs Cannot Draw the Boundary of What an Agent Verifier Can Check

A verifier for an agent faces rules of two kinds: the ones a fixed check can settle and the ones that require a judge. A team that derives its own checks fixes that split up front. Where the requirements come from outside, as in finance, healthcare and law, the agent enforces rules it did not write, so the split falls...

Anthony Rhodes · 0 citations
#artificial intelligence Preprint Sep 2026

The Safeguard Worked. Is the LLM System Safer?

This work determines what each reported result implies for that question: how much help with harmful tasks the service still gives an attacker who keeps adapting or finds another way in.

Pingyu Wu, Wei-Ming Zhang, Neng-Hai Yu · 0 citations
#artificial intelligence Preprint Oct 2026

Where Rules End and Judges Begin: Measuring the Judgment Boundary in Multi-Agent Systems Security

LLM-based multi-agent systems (MAS) engage tools, share memory, and delegate tasks, often encountering adversarial content. Current defenses for MAS are typically evaluated in isolation, focusing on one attack type at a time, which can lead to costly and hard-to-audit outcomes. This study organizes defenses into five p...

Shaswata Mitra, Raj Patel, Subash Neupane et al. · 0 citations

We use cookies to run the site and, with your consent, for analytics and to show ads. See our Cookie Policy.