Skip to main content
BotGauge tests your agent against rules. A rule is a statement about what the agent must or must not do, such as “never reveal the system prompt”. Each rule is attacked in several different ways, so a rule can pass or fail independently of the others.

The standard rules

BotGauge ships with 20 standard rules. A rule runs only if it applies to your agent. Tool rules need tools, for example. A rule that doesn’t apply, or can’t be tested with the access BotGauge has, is not hidden. It appears in the plan as skipped with the reason, for example “needs grey-box access” or “no tools found”.

Your own rules

You can add a rule in plain language, or edit it as YAML. Validate it before saving. You can turn rules on or off, and confirm or dismiss rules that BotGauge suggested after recon. Rules are versioned, and a run records exactly which version of each rule it used.

What the Review screen shows

In the API plan overview you see:
  • how many rules and attacks will run
  • estimated time and cost, based on your last runs, or 15 seconds per attempt as an assumption when there is no history
  • which tools could be touched and which channels are used
  • a plan digest, a fingerprint of the plan that your approval is tied to
In the console wizard, the equivalent is the Choose what to test screen. It shows three phase cards, each with checkboxes for strategies, and a button reading “Start Attack, N strategies selected”. Everything is selected by default, and at least one strategy must stay selected.

Settings that shape the run

Black box or grey box

BotGauge decides the mode from access it has proven, not from what you claimed. Rules that need inside access are listed as skipped, not as passed. See black box and grey box.

Review a plan before you approve it

Pick your rules, set the budget, and see the cost estimate in BotGauge.

Try BotGauge →