Hosted gate · Scorecard · Nov 10 2026, main 6ceb532
21 guarantees,
and how each is checked
The AgentGuard® hosted gate makes 21 guarantees. All 21 pass a property test. 4 are proven on production in full, 3 in part, and 14 are not proven live.
How these limits are checked
Each guarantee has an id and a property test. A property test does not check a few examples: it generates thousands of requests and runs each one through the same request handlers that serve agentguard.run.
On November 10, 2026 the suite ran 30 properties, 1,000 generated requests each, and every one passed. The suite was also given 45 deliberate bugs, one at a time, and it caught all 45. Open a row below to read the bugs that were injected for it.
A test suite shows what the code does with generated requests. It does not show what the deployed service does. So each row also says whether the guarantee has been checked on production with real requests, and on which date.
G09, G30, G31 and G33. Checked in full with real requests.
G08, G15 and G34. Each row says which part was checked and which was not.
Proven by the test suite, and not yet by a production probe.
The 21 guarantees
Generated inputs per run is the number of generated requests the guarantee's properties run by default. Injected bugs caught counts the deliberate bugs put into a copy of the gate code for that guarantee, and how many made its test fail.
| Id | Guarantee and test file | Generated inputs per run | Injected bugs caught | Proven on production |
|---|---|---|---|---|
| G01 | A block or escalate decision never executes or signs an allow. Test file 2 injected bugs, 2 caught
| 1,000 | 2 of 2 | not proven live |
| G02 | A caller's risk score can only make a decision stricter, never looser, for any policy and request. Test file 1 injected bug, 1 caught
| 2,000 | 1 of 1 | not proven live |
| G03 | The money window cap is never exceeded, even with many allows racing at once. Test file 2 injected bugs, 2 caught
| 2,000 | 2 of 2 | not proven live |
| G04 | Once a policy is pinned on a vendor key, a policy sent in the request never changes the decision, and the receipt says the request policy was ignored. Test file 1 injected bug, 1 caught
| 2,000 | 1 of 1 | not proven live |
| G05 | Per-recipient contact caps, the fleet contact cap and calling windows are never exceeded or bypassed, across time zones; a contact to an unknown time zone is held, not guessed. Test file 5 injected bugs, 5 caught
| 4,000 | 5 of 5 | not proven live |
| G06 | A contact in a category the recipient opted out of is always refused. Test file 1 injected bug, 1 caught
| 1,000 | 1 of 1 | not proven live |
| G07 | A request carrying a content field, or text over the length limit, is refused, exactly as the /vendors terms define both. Test file 2 injected bugs, 2 caught
| 1,000 | 2 of 2 | not proven live |
| G08 | Every signed receipt verifies with the published key, and changing any one field of it makes verification fail. Test file 2 injected bugs, 2 caught
| 1,000 | 2 of 2 | In partNov 9 2026The live verifier accepted the published demo receipt and rejected a copy with one amount changed. One receipt and one changed field, not every receipt kind. |
| G09 | An action with no matching rule is blocked (default deny), and a claimed capability below the rule's requirement is blocked. Test file 2 injected bugs, 2 caught
| 2,000 | 2 of 2 | Proven on productionNov 9 2026The production sandbox blocks an action typed toString and one typed __proto__. |
| G10 | Only money going out counts toward caps; a payment taken in never does. Test file 2 injected bugs, 2 caught
| 2,000 | 2 of 2 | not proven live |
| G11 | A held action becomes an allow only through the approver's own link, before it expires, and is decided once. Test file 3 injected bugs, 3 caught
| 1,000 | 3 of 3 | not proven live |
| G12 | The approver is the operator's setting, never the agent's, and the approval link never goes back to the agent that asked. Test file 2 injected bugs, 2 caught
| 1,000 | 2 of 2 | not proven live |
| G13 | A payee or customer reference never appears in the clear in a receipt, a response or anything the gate stores. Test file 1 injected bug, 1 caught
| 1,000 | 1 of 1 | not proven live |
| G14 | Without a vendor key the gate is a sandbox: it stores nothing, counts nothing and never speaks for a real tenant. Test file 1 injected bug, 1 caught
| 1,000 | 1 of 1 | not proven live |
| G15 | The gate fails closed: if it cannot read or write its store, or cannot sign, the answer is block; a paused tenant is blocked for everything. Test file 2 injected bugs, 2 caught
| 1,000 | 2 of 2 | In partNov 10 2026A paused tenant's new request is blocked on production. A store or signing failure was not induced on production. |
| G16 | With a vendor key the gate counts and keeps time itself: spend, contact counts and times the caller sends never change a decision. Test file 2 injected bugs, 2 caught
| 1,000 | 2 of 2 | not proven live |
| G30 | An action names itself with plain codes: a type that is not a string, a currency that is not a three-letter code or a target system that is not a short code is refused, and nothing is decided, signed or stored from it. Test file 3 injected bugs, 3 caught
| 2,000 | 3 of 3 | Proven on productionNov 9 2026Three malformed requests answer 400 invalid_action_shape on production, and an ordinary refund is still allowed. |
| G31 | While a tenant is paused, a hold that was already waiting cannot be approved or denied; no receipt is signed for it until the pause is lifted. Test file 2 injected bugs, 2 caught
| 1,000 | 2 of 2 | Proven on productionNov 10 2026With a test key: approve and deny on a paused tenant's open hold answer 409 tenant_paused. |
| G32 | At a recipient's contact cap, the counts a caller sends never change the keyed decision (the contact half of G16, reached on purpose). Test file 2 injected bugs, 2 caught
| 1,000 | 2 of 2 | not proven live |
| G33 | An amount above a rule's Test file 2 injected bugs, 2 caught
| 1,000 | 2 of 2 | Proven on productionNov 10 2026Under a pinned key, a refund above the auto-approve limit is held for a person. |
| G34 | Words an agent chose never reach the person who decides: the approval email, text message and page show the operator's own label for the tenant, and the agent's id only as a labelled code, never inside a sentence. Test file 5 injected bugs, 5 caught
| 1,000 | 5 of 5 | In partNov 10 2026The approval page and the approval email show none of the planted words. The text message was not exercised on production. |
The test files are in the tests/invariants folder of the gate's source. G30 to G32 share one file, and so do G33 and G34. Evidence for each production check is kept on file.
What this page does not say
- It covers the hosted gate. It does not cover the local plugin, Burn or the Spend package.
- A guarantee marked not proven live is tested on every change. No one has yet checked it against production with a real request.
- A guarantee proven on production was checked on the date shown. It is checked again by the test suite on every change.
- The gate decides and signs. Your code runs the action, and only your code can make the action wait for allow.
The full wording of each guarantee, how the suite works and how to rerun it are in the guarantees file. The gate's contract, the sandbox and the pilot are on the vendors page. To see a hold and an approval in code, read Contact humans with tool calls, enforced.