Safety packs
Start from curated rules while preserving surface scope and exemptions.
On this page
Choose the relevant pack
Open Safety Packs in the console. Review the pack description, covered agent or surface, rule effects, and required plan before installing. Governance bundles can group multiple packs for a supported agent workflow.
Inspect the rules
Read both the blocking conditions and their exemptions. An exemption for an editor can prevent a documentation patch containing a dangerous command string from being mistaken for executing that command. Removing a supposedly redundant rule can lose exemptions even when another rule has similar coverage.
Do not assume a pack for one agent covers every tool interface. Confirm canonical tool names, model prefixes, triggers, and target attributes using a real decision.
Install and observe
Use a test environment first. Review the resulting active policy and revision, run known matching and non-matching examples, and inspect shadow outcomes. Enable enforcement after checking the workflow impact.
Maintain the pack
When replacing or updating rules, compare the coverage and all narrowing conditions. Keep application-owned exceptions explicit. A curated pack reduces authoring effort; it does not remove the need to validate the environment, integration, or false-positive rate.