Skip to content
Platform Status

Secure

Risk Policies

The Risk Policies page configures the policies that scan agent session interactions for secrets, sensitive information, and prompt-defined risks. Open it from Secure > Risk Policies in the dashboard.

Access requirements

Section titled “Access requirements”

Viewing this page and creating, editing, or deleting policies require the org:admin scope. Access is included in the default Admin role but not the Member role.

Policy list

Section titled “Policy list”

The policy table shows each policy’s name, action, severity, categories or prompt, scope, audience, and created and updated dates. Each policy has an enabled toggle and row actions to edit or delete — deleting shows the impact and affected rule groups before confirming. Create a policy with New Policy.

Policy editor

Section titled “Policy editor”

The editor is a stepped wizard. Standard policies step through Detect > Scope > Action > Review; prompt policies through Guardrail > Scope > Evaluate > Action > Review.

Detect

Section titled “Detect”

Choose detector categories to enable: secrets, financial data, PII, government IDs, healthcare data, shadow MCP, destructive tool use, account identity, and prompt injection. Each category can be customized to enable or disable its individual rules — see Detection Rules for the full catalog.

Scope

Section titled “Scope”

Choose which session content the policy evaluates: select message types directly, or write a CEL expression for precise inclusion. An exemptions expression skips the whole policy for any matching message.

Action

Section titled “Action”

Decide what happens on a finding:

  • Flag or block — record the finding, or stop the interaction
  • Severity — a 0.1–10 severity score assigned to findings
  • Detection sensitivity — the confidence threshold for a match
  • Audience — evaluate for everyone in the organization, or target specific members and roles

Prompt policies

Section titled “Prompt policies”

Prompt policies add a natural-language guardrail: describe the behavior to detect in plain language, with AI-assisted suggestions, and an evaluate step to tune it before it goes live.

Blocked access requests

Section titled “Blocked access requests”

Policies that block access feed an approval requests queue where blocked resource-access attempts are reviewed and project-scoped access rules are managed.