Language Is a Security Surface for Agent Guards
We build LinguaGuardBench from the 1,220 labelled steps of TS-Bench AgentDojo-Traj: we translate only the user instruction into German, French, Turkish, Swahili and Amharic, and keep every tool call, observation and label byte-identical, so any change in a verdict is attributable to language alone.
ProofPaper ↗
Key points
- Step-level guards decide, before each tool call, whether an agent's next action is safe given the user's request and the trajectory so far.
- Users write those requests in many languages, while guard prompts and the benchmarks on which purpose-built guards are trained and evaluated are English.
- We ask whether a guard's verdict depends on the language of the request.
- The direction of the damage tends to follow guard size: open guards of 12-30B parameters block more benign steps (up to +5.0 pp false positives), and every significant loss of recall is in a guard below 10B (up to -7.4 pp).
Sources (1)
- [1]Language Is a Security Surface for Agent GuardsarXiv (AI, ML, NLP, CV, robotics, multi-agent) · Oct 15, 05:19 PM
We build LinguaGuardBench from the 1,220 labelled steps of TS-Bench AgentDojo-Traj: we translate only the user instruction into German, French, Turkish, Swahili and Amharic, and keep every tool call, observation and label byte-identical, so any change in a verdict is attributable to language alone.
Step-level guards decide, before each tool call, whether an agent's next action is safe given the user's request and the trajectory so far.
Extractive summary: sentences quoted from the sources.
Before this
- Oct 15, 2026Shortcut Sensitivity in Agent-Safety Evaluations
- Oct 15, 2026StepFun Releases Step 5 Preview Open Weights: 600B MoE, 27B Active, 1M Context
- Oct 14, 2026Datalab Releases OmniParseBench: An Open OCR Benchmark With 16,288 Pass/Fail Tests to Audit OCR Parsers
- Oct 14, 2026mistralai/Timestral-209M
- Oct 14, 2026How Block is building AI-powered security with OpenAI technology
- Oct 14, 2026LatentLoop: Scaling Looped MoE Models with Asymmetric Compute Allocation