Skip to main content
Unbound has four policy types: Cost, Model, Security, and Tool. Each has its own subcommand for type-specific creation. Generic commands (list, get, delete) work across Cost, Model, and Security; Tool policies use a separate policy tool subcommand.

Reference data

Before creating policies, pull the available user groups, models, guardrails, and tool types:

Generic commands (Cost / Model / Security)

There is no generic unbound policy create or unbound policy update. Creates and updates are type-specific — use policy cost create, policy model create, policy security create, or the policy tool subcommand family below.
The same type filter applies to type-specific list and update commands:

Cost policies

Set a monthly spend limit per user group:
See Cost Policies for all configuration options.

Model policies

Control which AI models are available to a group:
See Model Policies for all configuration options.

Security policies

Apply guardrails for PII, secrets detection, and model routing:

Routing sub-type flags

Routing has two sub-types — default-routing (swap the model on a sensitive request, shown below) and error-code-routing. Routing swaps the model rather than blocking or redacting:
See Security Policies for all configuration options.

Tool policies

Tool policies control shell commands and MCP tool calls. They use a separate backend and are reached via unbound policy tool.

List and inspect

Discover available targets

Create a terminal command policy

Create an MCP tool policy

Available actions: BLOCK, WARN, AUDIT, REQUIRE_SLACK_APPROVAL

Update a tool policy

Only the fields you provide are changed.
See Tool Policies for the full list of actions, NL rules, and canonical group targeting. All commands support --json for machine-readable output.

Tool Policies

Dashboard reference for actions, NL rules, and Slack approvals

Cost Policies

Dashboard reference for budget limits and spend controls