See what Omnodex would stop, then let it
Omnodex can act on tool calls as well as record them. Shadow mode, free, shows which calls it would have stopped. Guardrails, on Pro, stop or hold the calls you choose before they run, and tell the agent why.
Three modes, one command
Switch at any time. A first install offers shadow mode, and upgrading never changes the mode you chose.
Monitor
CommunityThe default. Every call is recorded, and risky ones are flagged. Nothing gets in your agents’ way.
omnodex enforce monitor Shadow mode
CommunityEach finding also says whether Omnodex would have stopped the call. The call still runs.
omnodex enforce shadow Guardrails
ProCalls your settings say to stop are stopped, or held for your confirmation, before they run. Everything else runs as usual.
omnodex enforce guardrails Start in shadow mode
Run shadow mode for a while before turning guardrails on. The findings it marks are the calls guardrails would have stopped, so you can see whether that would have helped or just got in the way, before you pay for anything.
In the hosted dashboard, the Would have blocked filter narrows everything to those findings, and a tile counts them.
Nothing stops until you say so
Out of the box, guardrails stop nothing. You choose what stops: deny, hold for confirmation, or record only, by rule or by severity, with exceptions for a path, a host or a command, and settings per project.
A shared policy in a repository can only make Omnodex stricter. It can never switch protection off or add exceptions.
Hosted dashboard, shadow mode, on generated demo data.
What each agent does with a held call
A stopped call is blocked and the agent sees the reason. A call held for your confirmation uses each agent's own prompt where it has one. Omnodex never approves a call: one it does not stop goes through your agent's own permission settings exactly as before.
Claude Code
Claude Code’s own permission prompt, with Omnodex’s reason.
OpenAI Codex
Codex cannot prompt from a hook, so the call is stopped and the agent is told to ask you first.
Google Antigravity
Antigravity’s own permission prompt, with Omnodex’s reason.
MCP proxy (Cowork Desktop and other MCP clients)
The call never reaches the MCP server, and the agent is told to ask you first.
Which calls each agent lets Omnodex check: Coverage.
When a check fails
If the rules cannot load or take too long, the call goes ahead and the failure is recorded. You can choose to stop such calls instead.
Agents cannot turn it off
Leaving guardrails needs a person at an interactive terminal to confirm. An agent's shell cannot do it, and Omnodex raises an alert when an agent edits its configuration.
What leaves your machine
On a machine connected to the hosted dashboard, these modes send per-rule counts: a day, a rule, a kind and a number. No paths, commands, hosts or other content.