Policies

​

Writing a policy

​

Actor

• Agent name - a specific agent, like Claude or Codex
• Agent review status - Unreviewed, Allowed, or Disallowed

​

Operation

• Type - the kind of operation: Read, Write, Destructive, or Unknown
• Tools - one or more specific tools, searchable, each tied to its integration (Gmail, GitHub, etc.); tools with no known integration show up as Unclassified
• Connectors - matches every call made through a specific CLI or MCP integration point (for example, Linear accessed through Claude.ai’s MCP connector)

​

Resource

• Provider - the upstream system a tool belongs to (GitHub, Gmail, etc.), or all providers
• Content type - matches a content tag you’ve defined (for example, “PHI” for a healthcare company) - scans both the request and the response

​

Response

• Alert - notify your team. Set a severity (Low, Medium, High, Critical) and a cadence (every time, or throttled to once every 5 minutes, 15 minutes, 30 minutes, 1 hour, or 24 hours). Alerts route to the Slack channel you’ve already connected under Connections.
• Enforce - restrict the matching call. Choose one:
  • None - monitor only
  • Block - prevent the call from proceeding. For a policy that scans a tool’s response (a content-type condition), the call has already run by the time it’s scanned, so Block instead redacts the response.
  • Require user approval - pause until the end user allows or denies it.
  • Require security approval - block until your security team grants a one-time exception.
  Add a message when you enforce - it’s shown to the agent or user when the policy triggers.

​

Policy preview

• Runs on - which event types the policy is evaluated against, derived automatically from your conditions: a policy scoped to a specific tool (by Type, Tools, Connectors, or Provider) runs on the tool request; add a Content type condition to that same policy and it also runs on the tool response; a policy with no tool-scoping condition (matching only on Actor or Content type) runs on all three - user prompt, tool request, and tool response
• Matches - the specific tools and agents the policy currently matches
• Then - the resulting action

​

Supported integrations

​

Example policies

​

Require security approval for GitHub writes and deletions

Name: Require security approval for GitHub writes and deletes

Operation:
  Type: Write, Destructive
Resource:
  Provider: GitHub

Enforce: Require security approval ("Blocked pending security review")

​

Require user approval before deleting a Linear issue

Name: User approval for Linear deletions

Operation:
  Tools: Delete issue

Enforce: Require user approval ("This needs your OK before it runs")

​

Alert when Cursor makes any destructive call

Name: Alert on Cursor destructive calls

Actor:
  Agent name: Cursor
Operation:
  Type: Destructive

Alert: Medium severity, every time

​

Alert when an unsanctioned agent is discovered

Name: Alert on disallowed agent discovery

Actor:
  Agent review status: Disallowed

Alert: Medium severity, every time

​

Block and alert on a custom regex match

Name: Block serious prod regex

Actor:
  Agent name: Cursor
Resource:
  Content type: Serious prod regex

Alert: Medium severity, once every 30 minutes
Enforce: Block ("Can't use this regex")

​

Block API key leaks in any session

Name: Block API key leaks

Resource:
  Content type: API keys

Enforce: Block

​

Get help