Skip to main content

Guardian Agent

V2 console

This card lives in Policy Engine > LLM Gateway at web.quilr.ai/policy. Edits join the shared draft and take effect once you review and publish a revision.

Turn on Guardian's coding helpers and task-adherence checks for matching requests. Runs at the request stage.

Guardian Agent card collapsed, showing Guardian, Coding helpers, Task adherence and After Guardian runs rows

Sections​

SectionWhat it doesAdd button
GuardianThe master switch. Off here switches off every Guardian check below for that scope.Add settings
Coding helpersOn coding requests: a dependency security check and current-version suggestions, each switchable.Add
Task adherenceChecks that the model stays on the task the user asked for.Add
After Guardian runsFollow-up rules that tag a severity on what Guardian found.Add follow-up

Applies on assistants, bedrock, chat, copilot, responses, sdk_check and vertex.

Task adherence section listing per-application configurations with sensitivity and Nudge or Block

Settings​

Every add button opens the Guardian settings dialog. Each control is a three-way switch, so one configuration can change a single setting and leave the rest to a broader one.

Guardian settings dialog with Leave as is, On and Off switches for Guardian, Coding helpers and Task adherence, a Reads as preview, and Severity

SettingOptionsDefaultNotes
GuardianLeave as is, On, OffOn when opened from GuardianMaster switch for everything below.
Coding helpersLeave as is, On, OffLeave as isWhen On: Dependency security check (flags vulnerable packages in generated code) and Latest version suggestions (suggests current package versions). Both ticked by default.
Task adherenceLeave as is, On, OffLeave as isWhen On: sensitivity and action.
Task adherence sensitivityLow, Medium, HighMedium
Task adherence actionNudge, BlockNudgeNudge adds guidance to the response; Block rejects it.
SeverityNot set, Very low ... Very criticalNot setReported only; never changes what happens.

Leave as is keeps the value from a broader configuration. At least one control must be On or Off.

Follow-up rules​

Add follow-up opens Guardian follow-up. When is one of: Guardian blocked, at least N findings (N from 1), or a finding type. The rule then tags a severity. Guardian results are request-stage fields; they are not visible on the response leg. The highest severity among matching rules is reported.

Example​

secure_coding_guardianrequest

runs on requestpriority 700

WhenRequested modelmatches pattern*code*
Then
Guardiantrue
Dependency security checktrue
Latest version suggestionstrue
Task adherence sensitivityhigh
Task adherence actionblock

Scoping and precedence​

  • Applies to: Everyone, People, Smart group, Application, App tag, Requested model, Provider, API surface, Environment, Prompt text, Tool, Source network, or Except....
  • When several configurations match, the highest-priority one wins per setting.
  • Off on a narrower scope beats On for Everyone, so you can exempt one app or group.
  • Need Guardian only for certain languages, repos or request metadata? Use Add configuration at the bottom of the card.

Legacy app setting​

Replaces each app's Guardian Agent settings section while the Policy Engine is on.