Loading…
Open-Policy Exchange
~5 min to deploy
Codex Blast-Radius Gate
Scores every Codex tool call by blast radius and escalates anything that could touch production before it runs.
For: Teams running Codex with repository and shell access
SOC 2 CC8.1ISO 27001 A.8.32Agent action evidence
What it enforces
Production target escalation
Escalates any tool call whose resolved target is a production environment.
Estimated blast-radius ceiling
Escalates any action with an estimated blast radius over the encoded threshold.
Unapproved tool block
Blocks tool calls outside the approved tool list for this repository.
codex-blast-radius-gate.yaml
# Codex Blast-Radius Gate
# Fork: set the blast-radius threshold and the approved tool list.
# Wire at PreToolUse in .codex/hooks.json.
apiVersion: decionis.dev/v1
kind: PolicyPack
metadata:
name: codex-blast-radius-gate
surface: codex
standards: [SOC2-CC8.1, ISO27001-A.8.32]
defaults:
mode: shadow
emit_dossier: true
fail_closed: true
approved_tools: [read, edit, search, test_runner, build]
rules:
- name: production_target_escalation
when: "tool_call.resolved_env != null"
decision: |
ESCALATE IF tool_call.resolved_env == 'production'
ALLOW OTHERWISE
reason_code: production_target_requires_approver
- name: blast_radius_ceiling
when: "tool_call.estimated_blast_radius_usd != null"
decision: |
ESCALATE IF tool_call.estimated_blast_radius_usd > 10000
ALLOW OTHERWISE
reason_code: blast_radius_over_threshold
- name: unapproved_tool_block
when: "always"
decision: |
BLOCK IF tool not in approved_tools
ALLOW OTHERWISE
reason_code: tool_not_on_approved_list
Fork it, change the thresholds to match your environment, and deploy in shadow mode first — it defaults to listen-only so nothing in your live pipeline changes.
How to install it
Follow the install path for this surface, then paste the forked YAML as your policy config.
What to do next
This recipe is one step in a path. The same five steps apply to every recipe in the exchange.
- Simulate this recipe
Run the policy against a realistic action in the browser. Push it past what the rules allow and watch the verdict come back. No account.
- View the signed Decision Dossier
See exactly what was decided and why: the rule that fired, the evidence it read, the policy version in force, and an Ed25519 signature you can verify yourself.
- Deploy in shadow mode
Measure what the policy would have caught on your own traffic without touching the live path. Every recipe defaults to shadow, so the first deployment carries no execution risk.
- Connect a real workflow
Point the same policy at the system where the action actually originates — a checkout, an ERP posting, a Zap, an agent's tool call.
- Share the verified result
Publish the proof: a public verification link, an embeddable badge, a PR comment, or an anonymized shadow-mode finding. This is how the next person discovers Decionis.