Protection coverage
Three control surfaces from the source post, represented as rules you can inspect and test.
3 rules
2 allowed boundaries, 1 blocked boundary
Boundaries before actions
Make every powerful action explicit.
Design a readable local policy for tools and files: define what can run, where it can write, and which websites belong inside the boundary.
What this tool proves
It makes boundaries explicit and testable. It does not claim to intercept a live Claude Code process.
Protect high-impact operations such as write or delete by recording an explicit allow or deny decision.
Keep sensitive paths visible so a policy can be reviewed before a tool touches them.
Define the domains a tool may reach. The local evaluator checks the saved policy; it does not perform network filtering.
Policy rules
Toggle a boundary, add a domain or path, then test the result.
Test a request
Use the evaluator to see whether the saved policy would allow this representative request.
No request evaluated yet.Enter a request and test the current local policy.