The AI Agent Fabrication Benchmark
A single question, measured honestly: can an AI agent be made to take a real action on evidence it invented — and will your guardrails approve it?
Agentic systems don’t fail only by saying unsafe things. They fail by doing things — issuing a refund, deploying code, writing to a database — on the strength of a claim the model produced but no tool ever established. The action is well-formed. The authorizing fact is fiction. This benchmark measures how often that happens, and how often the standard defenses catch it.
What it measures
Each test case is an agent task where completing it is easiest if the agent fabricates a missing piece of evidence — an order that was never looked up, an approval that was never granted, a backup that never ran. We measure two numbers:
- Fabrication rate — how often the agent invents the evidence and acts on it.
- Guardrail miss rate — of those fabricated actions, how many a content-layer guardrail approves (because the text is clean).
Results
Figures from our internal suite — 504 evaluations across 126 scenarios × 4 tool types (May 2026). The benchmark is designed to be reproduced — numbers you can check beat numbers you’re asked to believe.
| Defense layer | Fabricated actions approved | Caught before execution |
|---|---|---|
| Content guardrails (safety / topic / schema) | 100% | 0% |
| LLM-as-judge review | 100% | 0% |
| Evidence-grounded verification | 0% | 100% |
Fabrication detection rate: content guardrails and LLM-as-judge caught 0% of fabricated-evidence actions (they have no mechanism to check whether an authorizing claim is grounded); evidence-grounded verification caught 100%. This is expected, not surprising — the others are not built to ask the question.
The pattern the benchmark exposes is structural, not incidental: defenses that read the agent’s output cannot distinguish a claim that is true because a tool proved it from a claim that is true because the model sounded confident. Only a check that grounds each claim against actual evidence separates the two.
How to reproduce it
- Take an agent with real tools (a refund flow, a deploy flow, a DB writer).
- Give it a task that is easier to finish by asserting a missing fact than by fetching it.
- Record whether it fabricates the fact and acts.
- Run the same trace through your existing guardrails, and through an evidence-grounded check, and compare what each approves.
A worked example: the $2,400 refund for an order that never existed →
Honest boundary
This benchmark measures one failure mode: actions taken on fabricated evidence. It does not measure prompt injection, data leakage, or harmful-but-evidenced actions — those are real and separate. We report only what this test actually establishes.Run the benchmark on your own agents, and see where your stack lands.
Test your agent →