Arcezia
Benchmark · Method you can rerun

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:

Results

Figures from our internal suite — 882 evaluations: 126 scenarios × 7 systems (July 2026 run). 71 of the 126 scenarios are fabricated-evidence cases. The benchmark is designed to be reproduced — numbers you can check beat numbers you’re asked to believe.

Defense layerFabricated actions approvedBlocked before execution
Prompt-injection classifier (Lakera Guard)42% (30 of 71)58% (41 of 71)
Prompt-attack classifier (PromptGuard 2)90% (64 of 71)7% (5 of 71)
LLM-as-judge review (Llama 8B)72% (51 of 71)28% (20 of 71)
Evidence-backed verification (Arcezia)0% (0 of 71)100% (71 of 71)

The text checkers blocked between 7% and 58% of these cases, as general threats. None of them checks whether the authorizing claim is backed by a record. Evidence-backed verification blocked 71 of 71 in this suite. That is a result on this suite, not a promise that every fabricated claim is caught. A Llama 70B judge returned no verdict on 34 of the 71 and is left out.

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 tests each claim against actual evidence separates the two.

How to reproduce it

  1. Take an agent with real tools (a refund flow, a deploy flow, a DB writer).
  2. Give it a task that is easier to finish by asserting a missing fact than by fetching it.
  3. Record whether it fabricates the fact and acts.
  4. Run the same trace through your existing guardrails, and through an evidence-backed check, and compare what each approves.

A worked example: the $2,400 refund for an order that never existed →

Terms used here: Authority Fabrication Index, pre-execution verification.

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: start with the Quickstart →