Skip to content

Tool Approval Matrix Compiler

Pair withAgent Tool Blast Radius Mapperto validate risk-tier assumptions before enforcement.

What This Tool Does

The Tool Approval Matrix Compiler produces a single allow, ask, or deny decision for each tool capability across Codex, Claude, and managed MCP policies. Define your rules once and it compiles the cross-platform matrix, so an agent's permissions stay consistent and least-privilege no matter which runtime enforces them. It runs entirely in the browser.

Last updated:

This tool is provided as-is for convenience. Output should be verified before use in any production or critical context.

Agent Invocation

Best Path For Builders

Browser workflow

Runs instantly in the browser with private local processing and copy/export-ready output.

Browser Workflow

This tool is optimized for instant in-browser execution with local data handling. Run it here and copy/export the output directly.

/tool-approval-matrix-compiler/

For automation planning, fetch the canonical contract at /api/tool/tool-approval-matrix-compiler.json.

How to Use Tool Approval Matrix Compiler

  1. 1

    Describe tool risk and capabilities

    Provide each tool's risk level and capabilities (read, write, network, shell, secrets) plus a default fallback action.

  2. 2

    Compile platform decisions

    Run the compiler to produce allow/ask/deny decisions for Codex, Claude, and managed MCP policy surfaces.

  3. 3

    Review summary distribution

    Check allow/ask/deny counts per platform to spot over-permissive defaults or overly restrictive enforcement before rollout.

  4. 4

    Copy policy snippets

    Use generated JSON snippets for codex policy, claude policy, and managed MCP policy as your deployment starting point.

  5. 5

    Deploy in dry-run first

    Apply policies in observation mode, monitor denials and escalation traffic, then promote to enforcement after clean telemetry.

Frequently Asked Questions

What does Tool Approval Matrix Compiler generate?
It generates cross-platform allow/ask/deny decisions for each tool and outputs policy snippets for Codex, Claude, and managed MCP workflows.
How are decisions computed?
Decisions are deterministic and based on declared risk level plus capabilities like shell, write access, network, and secret handling.
Can I set my own default action?
Yes. You can set a default fallback (allow, ask, or deny), and rule-specific logic then tightens decisions for higher-risk capability combinations.
Should I enforce output immediately?
Start in dry-run or observation mode first, review denial and escalation telemetry, then move to enforcement once behavior is stable.
Is this a replacement for security review?
No. It accelerates policy drafting, but final approval should still include human security review for high-impact production tools.