Back to Documentation

The Behavioral Firewall

Where protection applies, what needs setup, and what a review cannot enforce.

Review is not enforcement

Installing the extension and running a review does not put every agent behind a firewall. A control needs to be configured on the path of the action it is meant to govern. Check the active configuration and the limits shown by your installed version.

Protect Claude Code

The editor command DeepSweep: Protect Claude Code offers a separate settings change. Choose the scope, inspect the proposed rules and approve them before anything is written. Those rules rely on Claude Code matching paths and command prefixes; they do not inspect all command contents or cover every alternative way to perform an action. DeepSweep: Undo Claude Code Protection can review the protection changes it recorded.

MCP gateway boundaries

An MCP review does not route or block traffic. If you use a gateway, check which connections pass through it and whether it enforces decisions or only records them.

Do not assume complete coverage

Reviewing a permission, exporting a policy and enforcing a tool call are different actions. Do not assume automatic rewriting, quarantine or termination across every editor, agent or shell. Keep a recovery path for any configuration you change.

Govern your own environment

Install the extension and review the findings. Sign in free for two applied fixes. Upgrade to continue applying supported fixes without that limit and export an authorization policy document. Exporting the document does not install or enforce its rules.