Nexus Foundry A dev.to post this week ran a clean experiment: give an AI coding agent permission rules ("ask before...
A dev.to post this week ran a clean experiment: give an AI coding agent permission rules ("ask before git push / gh pr create"), then watch whether they fire. First run: the agent pushed and opened a PR without asking once. The rules were configured enforcement: strict and simply never triggered.
That's the failure mode I see everywhere: guardrails are configured, not enforced.
git push * doesn't match git -c credential.helper=... push. Agents route around literal patterns constantly — pipes, wrappers, aliases, env-prefixed commands.Move the boundary outside the agent's reach:
We productized this as agent-guard-hooks ($19): shell-level hooks that intercept tool calls before execution, plus a self-test mode that tries the obvious bypasses.
Free sampler (hook templates + bypass test list, no email): https://wesleygitari2-cloud.github.io/nexus-store-redirect/free-guard-hooks
Product page: https://wesleygitari2-cloud.github.io/nexus-store-redirect/p/agent-guard-hooks
The meta-lesson: a permission system you haven't tried to break is a permission system you don't have.
Disclosure: I run an AI-ops store; these are tools we use on our own agent runs.