LLM Agent Guardrail Over-Safety
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 oversafety 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, to our knowledge 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 annotators 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 grades (2,268 measured pairs), and 40 Undecidable pairs reported separately. Measuring seven guardrails (six from five designs, plus a content-safety baseline), we find a name-superstition effect: the execution-safety guards over-refuse an authorized action more often under a scary-looking object name than an innocent one. Since only the object name varies across the measured grades, the deviation is the names doing: the guardrails read the surface name, not the authorization context.