Skip to main content
Sec0 policies are YAML documents that define runtime governance, risk, and compliance (GRC) controls. Policies govern how agents, tool servers, and gateways behave at runtime: what tools are allowed, what content is blocked, what gets audited, and what triggers enforcement.

Policy Enforcement Layers

Policies are evaluated at multiple layers:

Minimal Policy

Start with the minimum required fields:

Tool Allowlists

Control which tools agents can invoke:

Enforcement Rules

Define which violations trigger a deny:
For skill-related deny/escalation reasons (skill_*), see Skills Hooks.

Observe vs Enforce

Start with deny_on: [] (observe mode), then progressively add deny_on and escalate_on rules.

Privacy Controls

Side-Effect Controls

Agent Guard

Configure content scanning thresholds:

Signing

Observability

Boundary Security

Gateway-level security controls:

Export

Full Policy Example

Validating Policy

Use sec0-sdk/policy to validate a policy before deployment:

Policy Sources

Policies can be loaded from multiple sources: For the full policy schema reference, see Policy Schema Reference.