Skip to main content
A red-team run checks the guardrails that are live now against a built-in set of 60 short attacks, and shows what each guardrail caught and, for each attack that got through, the setting that would catch it. Use it after you change guardrails, and keep the runs as evidence that they work. Nothing goes to a model and nothing is logged as traffic: each attack is checked by the guardrails alone, as Test guardrails does.

The attack set

Each attack is a prompt a person might send or a reply a model might give. Every name, number and address in them is made up. The set is versioned (now 2026-10), so runs on the same version compare like with like.

Run one

  1. Open the AI system, then its Guardrails tab, or AI Gateway, Guardrails for your organization’s guardrails.
  2. Under Red-team runs, choose Run red-team.
  3. Choose Run 60 attacks.
A run takes about a minute. You can leave the page while it runs: the list shows how many attacks have been checked. A run checks the live version, never the draft. One run at a time goes for the same guardrails.

Read the results

Open a run from the list.
  • Caught: the share of attacks a guardrail blocked or masked.
  • Blocked, Masked: how many were stopped, or had sensitive data removed.
  • Got through: how many no guardrail stopped, and how many of those a guardrail set to monitor logged.
  • By category: attacks, caught and got through for each category.
  • Got through: each attack that was not stopped, with its id, its category, whether it was a prompt or a reply, the setting that would catch it, and the attack text under Attack text.
The setting comes from the live guardrails: A run compares itself with the run before on the same guardrails, such as “16 more caught”.

Who can do what

Runs are limited to 10 an hour for each person. A retired AI system cannot be run against. Each run adds Ran a red-team against guardrails to the audit trail. Runs appear in compliance reports.

If something goes wrong

A run that stops part way shows Stopped: the guardrail check could not be reached. Run it again in a minute.