← All guides · Published November 14, 2026 · Reviewed November 14, 2026 · By the Ingenious AI team · 6 min read
How Do You Test a Block Policy Before Deploying It?
The short answer: you run the draft policy through AgentBlock's pre-deploy simulator at /tools/simulator. It evaluates the policy — the one in your builder cookie, or the default if you have not built one — against every known agent and the key paths you give it, and shows the verdict each combination draws before a single request is affected. It is the approval gate in the workflow: build, simulate, read the surprises, then deploy and verify.
Build my block kit — free · Test a policy in the simulator first
What is the AgentBlock simulator?
the free pre-deploy tool at /tools/simulator that runs a draft policy against the known-agent database and your key paths, reporting the decision each agent would receive on each path. It changes nothing live; it is the rehearsal that makes the production deploy a formality.
Why rehearsal is a separate step
Every production incident in these guides shares a biography: a policy that was reasonable in the builder met the real site and did something its author did not picture — a fence covering a shared landing page, a retrieval block taxing citations nobody had counted, a utility agent caught by a substring. The gap is never intelligence; it is that a policy's consequences are combinatorial — 21 agents times dozens of paths times caps and exceptions — and no one holds that product in their head reliably.
A simulator holds it for you. The discipline it creates matters more than the tool: deployment stops being the moment of discovery. By the time a kit ships, its author has already seen its verdicts, which converts the post-deploy log review from incident triage into confirmation.
What the simulator evaluates
The simulator takes the policy as the generator built it — per-agent decisions, allowlist subtraction, path rules, rate caps — plus the paths you supply, and works the matrix. For each known agent on each key path you see the effective outcome: served, refused by identity, refused by fence, capped past budget. The watch entries appear as what they are — not matchable by name — rather than being quietly assumed into a result.
Supply paths that represent your real risk surface: the homepage and a top article (the public face), a product or pricing page (the citation target), checkout and login (the fences), a preview URL (the leak), and the page your customers share most (the utility test). Six to ten paths cover the shapes that matter; the simulator's value scales with the honesty of that list.
The three surprises it exists to catch
First, the friendly-fire surprise: something you depend on — the preview fetcher above all — drawing a refusal on a path people share. Second, the fence-collision surprise: a wildcard written for /account or /admin covering a public path that merely shares a prefix with private space. Third, the invisible-tax surprise: a retrieval agent you meant to keep drawing blocks across your citation-bearing pages because a class default outranked an intention you never converted into a flip.
All three are one-line fixes in simulation and multi-week mysteries in production, because production symptoms present in other teams' dashboards — marketing's share numbers, support's login complaints, SEO's citation reports — long before anyone suspects the crawler kit.
Where simulation sits in the loop
The full loop, as the fleet runs it: build the policy in the builder; preview impact against your real log to price the decisions; simulate the draft against key paths to catch the collisions; deploy the artifact; verify the deployed kit against the policy by ID and hash; then read the first week's verdicts as confirmation. Simulation is step three of six — the last free mistake, positioned exactly before mistakes start costing.
For agencies, the simulator output doubles as the client approval artifact: a legible matrix of what will be refused where, signable by a non-technical owner in a way a Worker script never is. Approval gates work when the approver can see the thing being approved.
Five actions to take today
- Simulate every draft, not just the first. Policy edits collide in the same ways whether they are made at launch or in year two.
- Choose paths that can embarrass you. Homepage, top article, pricing, checkout, login, preview, and your most-shared page — the risk surface, not the brochure.
- Read the refusal column first. Friendly fire and fence collisions live there; confirm every refusal is one you intended.
- Check the retrieval rows on citation pages. Your allowed agents must actually be allowed on the pages answers cite.
- File the simulator output with the approval. It is the dated record of what the policy was expected to do — the baseline the first week's logs are read against.
Worked example: the fence that ate a landing page
Solstice Stays, a fictional vacation-rental group, wrote a path fence for its owner portal as /owners/* — and, in simulation, watched its highest-converting public page, /owners-guide-to-pricing, draw refusals for every agent. The wildcard could not tell the portal from the guide that shared its prefix, and neither, in production, would the Worker.
The fix took a minute: the portal fence narrowed to /owners/portal/* and the guide added as an explicit public path in the test set. The simulator re-ran clean across 8 paths and 21 agents.
The group's counterfactual is easy to price: in production, the original rule would have removed its best guide from every AI answer and every preview fetch for as long as it took someone to connect a traffic dip to a crawler rule — the exact mystery the simulator exists to prevent.
Frequently asked questions
Is the simulator free?
Yes. The simulator page and its API run against your builder policy — or the default policy if you have not built one — without a plan. It is part of the free core, alongside building the policy and the Cloudflare Worker download.
What policy does the simulator test if I have not built a kit?
The default policy: 20 verified agents blocked, the utility agent allowed, class defaults applied. That makes the simulator useful as a first exploration — you can see the strict posture's verdicts on your key paths before deciding what to flip.
Does the simulator use my real traffic?
That is the impact preview's job — it replays your server-log evidence against the policy. The simulator answers the complementary question: given these paths, what would the policy do? Owners run both; preview for economics, simulation for collisions.
Can I simulate watch-entry agents?
They appear as what they are: unmatchable by name. The simulator will not pretend a verdict for Atlas, Muse or Grok retrieval, because no name rule binds them — the same honesty the database grades enforce, applied to rehearsal.
How is simulation different from the kit verifier?
Sequence and object. The simulator tests a draft policy before deployment; the verifier tests the deployed artifact against the policy after deployment, by kit ID and hash. One prevents wrong policies; the other prevents right policies from being wrongly installed.
Related guides
- How to Block AI Scrapers and Bots from Your Website
- Which AI Crawlers Should You Allow?
- How Do You Block AI Bots on WordPress, Cloudflare, or Plain JS?
- Pre-deploy breakage simulator — test a policy before it ships
- Impact preview — your server log against a draft policy
- What Crawler Policy Should a SaaS Documentation Site Run?
- How Should a Creator or Portfolio Site Handle AI Crawlers?
- Incident: What Happens When a Block Rule Breaks Your Link Previews?
- Incident: How Blocking a Retrieval Crawler Quietly Costs You Citations
- Incident: How a Stale Kit Missed Meta's New Crawler Wave
- Block evidence — parse a log, build an evidence pack
- The dated agent database — 25 entries, graded