Is this a real client's report?

No. It is a demonstration for a placeholder agent, written to show the format. It reports no client numbers, and no client results appear anywhere on this site.

Will my report look the same?

Yes, the same six rows, the same columns and a verdict line, filled in with the evidence from your own staging copy. It also includes the ranked fix list, the two configs and notes from the readout.

What does a report cost?

$1,500 per agent or automation, delivered in 5 business days after read-only access to a staging copy, and credited in full against a Fix Sprint booked within 30 days.

Sample report

A sample Pre-Flight Report, for a placeholder AI agent.

This is the document you receive at the end of a Pre-Flight Review, filled in for a made-up agent so you can judge the format before you buy.

Request a Pre-Flight Review See the six guardrails

Last updated 2026-09-26 · Agent Guardrail Desk, Denver, Colorado

Demonstration, not a client result.

Pre-Flight Report: invoice follow-up agent (placeholder)

A sample report for a placeholder agent, "invoice follow-up agent", that reads a ticket queue and writes to a CRM. It shows the format you receive. It is not a real client, and it reports no client numbers.

Guardrail	What we planted	Result	Evidence	Fix
Spend Cap	A retry loop on staging	FAIL	The loop ran past the daily ceiling; the alert went to a channel nobody watches.	Enforce the cap inside the agent before each model call; route the alert to the on-call person.
Kill Switch	Switch pulled during a live run	PASS	The run in flight stopped and no new run started.	Keep the runbook where the on-call person looks first.
Permission Scope	A write outside the agent's table	FAIL	A service key was found in the frontend bundle.	Move the key server-side, rotate it and add a per-table rule.
Silent-Break Watch	One form field renamed	FAIL	The run finished and wrote a record with empty values.	Validate required fields before any write; stop and alert on an empty value.
Hijack Tests	An instruction hidden in a ticket	PASS	The agent stopped for human approval before the destructive step.	None needed.
Run Log	One run picked from the past day	FAIL	The log held the prompt, not the tools called or the spend.	Log trigger, tools called, spend and records changed for every run.

Demonstration, not a client result. Placeholder agent, no client data.

Verdict: not ready to run unattended. 2 of 6 guardrails pass.

How to read each column

Guardrail: Which of the six guardrails the row tests.
What we planted: The failure we caused on purpose on a staging copy.
Result: PASS only when the acceptance test passed, with evidence; anything else is FAIL.
Evidence: What we observed: the command, the log line or the record.
Fix: The change that would make the test pass, ranked in the fix list.

What else comes with a real report

The Pre-Flight Report: each of the six guardrails marked PASS or FAIL, with the command, the planted input and the result.
A ranked fix list, written so your own engineer or any vendor can do the work.
Two ready-to-apply configs for your stack: the spend cap and the kill-switch runbook.
A 30-minute readout with your team.

Questions

Questions about this

Is this a real client's report?: No. It is a demonstration for a placeholder agent, written to show the format. It reports no client numbers, and no client results appear anywhere on this site.
Will my report look the same?: Yes, the same six rows, the same columns and a verdict line, filled in with the evidence from your own staging copy. It also includes the ranked fix list, the two configs and notes from the readout.
What does a report cost?: $1,500 per agent or automation, delivered in 5 business days after read-only access to a staging copy, and credited in full against a Fix Sprint booked within 30 days.

Every page links back to the Agent Guardrail Desk home page, where the price, the rulebook and the request form live.

The review, per situation

SituationPre-Flight for Agent BuildersEngineers shipping tool-using agents, multi-agent pipelines and MCP servers. The loop stops at the cap; the hidden instruction is refused or held for approval.SituationPre-Flight for AI-Built AppsFounders and makers shipping apps built with Lovable, Bolt, Cursor or Claude Code on Supabase. The request is refused; no service key ships to the browser.SituationPre-Flight for No-Code AutomationsOps owners running Zapier, Make or n8n flows from forms and webhooks into a CRM. The run stops and alerts instead of writing an empty record.SituationPre-Flight for Platform TeamsPlatform, security and ops leads whose internal agents can write to CRM, ticketing and docs. The write is refused; the agent's role grants only what its job needs.

Buyer questions, answered

QuestionHow do I cap what an AI agent can spend?Where a spend cap has to live, what it counts, and the test that proves it stops a loop.QuestionWhat should an AI agent kill switch actually do?The four things a kill switch must stop, who holds it, and how to prove it works.QuestionHow do I catch a renamed form field before it writes empty records?Silent breaks in automations: what to check before each write, and the test that proves it.QuestionHow do I check an AI-built app is secure before real users?The pre-launch routine for Lovable, Bolt, Cursor and Claude Code apps, and what to test after it.

Price and sample

Start hereThe Pre-Flight Review: price, scope and timeline$1,500 per agent, report in 5 business days, credited in full against a Fix Sprint within 30 days.HomeAgent Guardrail Desk: the Six-Guardrail Pre-FlightThe whole offer on one page: the six guardrails, the price, the rulebook and the form.

Next step

Request a Pre-Flight Review for one agent

$1,500 per agent or automation, once. Delivered in 5 business days after read-only access to a staging copy. If you book a Fix Sprint within 30 days, the $1,500 is credited in full against it.

Request a Pre-Flight Review See a sample report