Guardian tab on AI Agent asset pages

Important Guardian Agents are available in private preview. Details in this topic are based on pre-release designs and an early build, and are subject to change before general availability.

The Guardian tab on an AI Agent asset page shows the date the agent was activated for Guardian enforcement, its action pass rate over time, and a log of every action Guardian intervened on.

Note This tab only shows data once the agent is actively guarded. For the conditions that must be true before that happens, go to Enabling Guardian for an agent.

For a view across every agent with Guardian enabled, go to the Guardian agents item in the AI Command Center sidebar navigation.

Guardian tab components

Screenshot needed

Component Description
Agent action pass rate over time A stacked bar chart showing the daily proportion of the agent's actions that passed (green) versus failed (red) Guardian evaluation.
Issue log

A table listing each action Guardian intervened on. Columns include:

  • Date: When the turn that contained the action started.
  • Verdict: Deny, Escalate, Flag, or Rewrite: The most severe verdict in the turn. If Guardian runs in monitor mode, a stopped action means that the action would have been stopped, and the call went through. For details, go to About Guardian Agents.
  • Issue: The technical identifier of the check that was triggered, for example block_email or redact_customer_email.
  • Agent version: The specific AI Agent Version involved.
  • Rule violated: The specific agent contract rule that the action violated, and the Agent Contract it comes from. The rule text is shown as it was when it was compiled, so later edits to the Agent Contract don't change it.

Use the filters above the issue log, date range (for example, Last 30 days), Verdict, Issue, and Agent version, to narrow the table to the issues you want to review.

  • The date range is required, and it includes the start and excludes the end.
  • If you select several values in one filter, an issue matches if it has any of them. For example, selecting Deny and Escalate shows issues with either verdict. An issue must match all of the filters that you use.
  • The Verdict filter matches the most severe verdict in the turn. The Issue filter matches the identifier of the check that was triggered. Because these identifiers are set when Agent Contracts are compiled, there's no fixed list, and an identifier that never occurred returns no results.
  • The log is sorted by date, with the newest issues first by default. You can also sort with the oldest first.
  • The log only includes agents that you're allowed to view. If a filter returns no issues, the log is empty.

You can't filter the log by rule, Agent Contract, or whether Guardian was enforcing or monitoring.

Click a row in the issue log to open a detail view with additional context about that action. The detail view shows a summary, the user's request, the agent's response, and the full reasoning chain: every step of the turn, including steps that were allowed, with the rules that applied at each step. For each step, it shows where in the flow it happened (prompt to model, model to tool, tool to model, or model to user), the decision, the rules that fired, and the input and output, when the payloads were collected. For more information, go to Set up AI Command Center.

Note TBC - the filters and their behavior come from the telemetry service specification (Groundwork, 2026-10-22). The frontend screens for the Guardian tab couldn't be read, so confirm the exact columns, which filters each screen shows (including the date range presets and whether a sort option is offered), and the detail view layout against a live build. The list of verdicts isn't final, so new values may appear. The issue detail screen may also still run on sample data in the early build.

Note The same pass rate chart and issue log also appear at the environment level, on the Guardian agents item in the AI Command Center sidebar navigation. That view adds an Agent column and filter, since it spans every agent with Guardian enabled instead of just this one.

What's next