Guardrails
Review how each guardrail is performing — fire rates, compliance trend and false positives — and set its name, category and priority
Guardrails are the safety and compliance checks AskRAI runs over an interaction. This page is where you review how they are performing — how often each one fired, against what, and how many of those were false positives — and where you set a guardrail's name, description, category and priority. Like every guardrail surface, it opens to the holders of View policies, guardrails and egress, read-only, and of Manage policies, guardrails and egress, who make those changes; Platform Admin holds both (Access). A Member does not see it in the console's navigation.
What a guardrail actually does is defined elsewhere. Its kind, the stage it reads, the action it takes and whether it is Active all live on the Admin → Guardrails page, which is also where guardrails are now created. Every editor here links there with Edit in Admin. See Guardrails (concept) for what those three decisions mean.

Each card carries the guardrail's category, its priority and a preview of its prompt — the fields this page owns.
What this page can and cannot change
| Field | Where it is set |
|---|---|
| Name, description, category, priority | Here. The editor in Admin authors name and description, but sets category and priority for you — Custom and 5 — with no control to change them |
| Kind, stage, action, status, judge model, per-kind configuration | Admin → Guardrails only |
| Which groups or agents a guardrail governs | The group, the agent, or a policy |
A guardrail that nothing lists screens nothing, for anyone. Guardrails are attached to a subject, never applied tenant-wide: a person's guardrails come from their groups, an agent's from the agent. This page has no attachment control. To put one into effect, add it to a group under Admin → Users → Groups (see Users, Roles & Groups), to an agent on the project's Team pane, or to a policy attached to either.
How the guardrails on this page behave at runtime
- Six kinds, five of them free. PII, regex deny, word deny, secret scan and link domain are evaluated in code and cost no model call. Only an LLM judge reaches a provider — and only a judge has a prompt.
- Three stages. A guardrail reads the user's question (Input), the generated answer (Output), or the arguments an agent is about to send to a tool (Tool call). A rule about how answers should be worded belongs on Output.
- Three actions. Block stops the turn, Warn lets it continue and leaves a record, Redact substitutes what it found and continues. One blocking guardrail is enough — there is no majority rule.
- Priority is evaluation order. The deterministic kinds run one after another in priority order, and the first one to block is the one reported as the reason. Judges run afterwards, at most three at a time. Once something has blocked, only the judges that would also Block are skipped — a Warn judge still runs, so it keeps firing on exactly the turns it was attached to watch. (A judge cannot be set to Redact: it returns a verdict, not the position of what it objected to.)
- Audit recording. Every evaluation, pass or fail, is recorded and counted in the analytics. No setting reduces this.
- Only Active guardrails run. A draft is listed and attachable and evaluates nothing. The status badge is in the editor here; the status itself is set in Admin.
Viewing guardrails
Three view modes, switchable from the toolbar:
- List view (default) — a card per guardrail with its name, category badge, priority chip, a preview of its prompt, and a fire badge.
- Table view — columns for name, description, category, priority, reporting level, fire count, fire rate and a sparkline trend.
- Analytics view — a compliance trend line, a category distribution breakdown, and a top-fired guardrails chart.

Table view sorts on Name, Category and Priority only — Description, Fires, Fire Rate and Trend carry no sort control. Note the pager: the list is ten guardrails to a page.
By default the list is in run order: lowest priority number first, so the guardrail that runs first heads it. Sorting, filtering and paging are all done by the server, so the sort applies to the whole set rather than to the page you are looking at.
The card (List) view relabels the category badge: compliance shows as Regulatory, quality as Behavioral, privacy as Legal, and custom as Procedural. The underlying names are what you see in the editor, the filter dropdown, and Table view.
Filter the list from the toolbar:
- Search — case-insensitive substring match across the name, description and prompt fields.
- Category — Safety, Compliance, Quality, Privacy, or Custom.
- Priority — a range of priority numbers, From and To inclusive, each applied as you type it. Leave either blank for no bound: From
40alone lists every guardrail at 40 or more. The lowest number runs first. - Reporting level — None, Alerts or All. This is stored metadata that no longer has an editor control and does not affect what is audited (see below); the filter is here because the value is still recorded and still shown in Table view.
Active filters appear as removable chips below the toolbar. Clear All lives inside the Filters popover, not next to the chips.
Creating a guardrail
Add Guardrail navigates to Admin → Guardrails, where authoring happens. That is the only surface carrying kind, stage, action and status — the four fields that decide whether a guardrail does anything at all — so a guardrail cannot be created from this page.
This page and Admin → Guardrails open to the same people, so everyone who can see this page can open Admin → Guardrails too. Add Guardrail needs Manage policies, guardrails and egress: for a holder of View alone it is held, saying so.
Once the guardrail exists, come back here to set its category and priority, and to watch it perform.
Editing a guardrail
Click any guardrail card or table row to open the editor. Name and description are edited in place from the header; category, priority and — for an LLM judge — the prompt are below.

The strip at the top is what this guardrail does at runtime — status, kind, stage and action — none of which this editor can change. It is shown because the fields beneath it read as the whole of a guardrail without it.
The Prompt field appears only for an LLM judge, and Save changes is held until it has one: a judge with an empty prompt asks the model nothing. Every other kind is refused by the server for carrying a prompt at all, so no prompt is offered for them.
Priority takes any whole number from 0 up, and the lowest runs first; the guardrails that ship with AskRAI sit between 5 and 40. A priority you have not touched never holds Save changes, so renaming a guardrail leaves its priority as it was.
Saving applies from the next turn onward, including turns in conversations already under way, and is in force everywhere within five minutes at the outside.
Platform guardrails
Guardrails that ship with AskRAI are read-only on both pages — an edit or a delete is refused. Neither List nor Table view marks them: the Platform badge appears once you open one, alongside the notice that it cannot be changed.

Every control is disabled and Delete is absent — the editor says so rather than letting you reach a permission error. To change one, duplicate it under Admin → Guardrails to get an editable copy.
Deleting a guardrail
Open the guardrail and click Delete at the bottom-left of the editor, then confirm. Deletion is permanent. Platform guardrails have no Delete control.
Field reference
| Field | Description | Required | Values |
|---|---|---|---|
| Name | Display name shown in the list | Yes | Free text |
| Description | Narrative explanation of the guardrail's purpose | No | Free text |
| Category | Classification used for filtering and the analytics breakdown. Carries no runtime meaning | No — defaults to Custom | Safety, Compliance, Quality, Privacy, Custom |
| Priority | Evaluation order, lowest first, and which blocker is reported as the reason | No | Any whole number from 0 up |
| Prompt | The rule an LLM judge puts to the model | Only for an LLM judge, and then Save is held without it | Free text |
Analytics
Switch to the Analytics view to see guardrail performance over a configurable date range. That view has its own date picker (with 30d/60d/90d presets) and a Channel filter, separate from the Analytics period picker used by List and Table view. The Analytics picker allows up to 90 days; the List/Table picker is limited to a 30-day span, the longest the fire badges can show. In both, a wider range, or a From after its To, is not applied: the reason appears under the date inputs, and the view keeps the last range it showed. A link to the Analytics view carrying such a range opens on the last 30 days. Each day of a range, and of the compliance trend, runs from midnight in your browser's time zone, as the conversation logs show their times.
- Compliance trend — the share of blocking guardrail evaluations that passed. Warn and Redact results are left out: they found something and let the turn through, so how often those fire is what the fire count and the Top Triggered chart show instead. It counts evaluations rather than conversations, so a message screened by three guardrails contributes three results.
- Category distribution — fires broken down by category.
- Top Triggered Guardrails — guardrails ranked by fire count, not by priority. Each bar's label also carries that guardrail's fire rate and, where one exists, its false-positive rate — the share of its fires later marked as false positives in the conversation logs. There is no separate false-positive chart. Clicking a bar opens that guardrail's editor, wherever it sits in the list and whatever the list's filters hide. A bar for a guardrail deleted since it fired says the guardrail no longer exists.
In List view each card shows a fire badge with the total for the selected range, and beside it the fire rate as a percentage of conversations plus a sparkline. The badge colour reflects the rate: green below 15%, orange from 15% up to 50%, red at 50% or more. Table view shows the same numbers as plain columns.
Troubleshooting
| Symptom | Cause |
|---|---|
| A guardrail never fires, however it is written | Nothing lists it. Attach it to a group, an agent, or a policy — or its status is draft, which is set in Admin. |
| Save changes stays disabled | The name is empty, it is an LLM judge with no prompt, or Priority holds something other than a whole number from 0 up. |
| Guardrails is missing from the console's navigation | None of the account's roles grants View policies, guardrails and egress or its Manage, both of which Platform Admin includes. Guardrails are reserved for their holders wherever they appear. |
| Editing a platform guardrail is refused | Platform rows are read-only. Duplicate one under Admin → Guardrails. |
Related pages
- Guardrails (concept) — kind, stage and action, and how an evaluation runs
- Admin → Guardrails — author a guardrail and set what it does
- Policies — attach a set of guardrails to a group or an agent, and ceilings to an agent
- Users, Roles & Groups — attach guardrails to a group
- Conversation Logs — review evaluation results and mark false positives
Knowledge Packs
Organize knowledge base content into collections with file uploads, content type selection, the organizations whose agents may search them, processing history, and bulk status management
Administration
Manage users, roles, groups, directory sync, organizations, sandbox testing, and platform configuration settings