Derbent
Policy gate and tamper-evident audit log for coding agents' MCP and built-in tool calls
- Pricing
- Open source
- Platforms
- CLI, macOS, Windows
- Version
- 1.0.0
- Listing updated
- today
Similar MCP servers
About Derbent
Derbent is an open-source MCP server for developer tools. It is available on CLI, macOS, Windows, Linux and self-hosted.
The README says Derbent sits between a coding agent and the tools it calls, whether those are MCP tools or a CLI's built-in shell and file-edit tools. Each call is checked against one set of rules that can allow, deny or hold it for approval, and every decision is written to a hash-chained receipt log stored in SQLite.
It ships as a single binary for Windows, macOS and Linux with no daemon or network listener. Claude Code, Codex, GitHub Copilot CLI and Antigravity CLI are described as connecting to it, and other MCP servers can be placed behind it so each agent only needs one Derbent entry. Calls that match an ask rule wait in a terminal UI until someone approves or denies them, or are denied after a timeout.
The project positions itself as a guard against mistakes and prompt injection with an audit trail, not as a sandbox. Developers running several coding agents on their own machines who want rules and a verifiable record of tool use are the intended audience.
What it does
- Allow, deny or ask rules
- Rules match by agent, tool and arguments, with the first matching rule deciding and project rules able to tighten them.
- Terminal approvals
- Calls marked ask wait for approval in the terminal UI or from a shell command, and are denied after 50 seconds by default.
- Hash-chained receipts
- Every call gets a receipt, and the verify command reports where the chain breaks if a receipt is edited, moved, inserted or removed.
- Built-in tool hooks
- A pre-tool hook sends a CLI's shell and file edits through the same rules as MCP tools.
- Tool pins and budgets
- Pins hold back a downstream tool whose definition changes, and budgets stop an agent stuck in a loop.
- Shared memory and handoffs
- Agents can keep notes per repository and leave tasks for one another.
Good for
- Require approval before an agent runs git push or other risky shell commands
- Keep a verifiable log of what each coding agent did during a session
- Route several MCP servers through one gateway with a single config entry
- Stop a runaway agent with per-tool call budgets
- Review and accept changes to downstream MCP tool definitions
Pricing
Open source
Apache 2.0 licence; no paid plan mentioned.
Derbent FAQ
Is Derbent a sandbox?
No. The README says it is not a sandbox, and an agent that can already run shell commands as the user can get around it.
Which CLIs does it support?
The README names Claude Code, Codex, GitHub Copilot CLI and Antigravity CLI, noting that Codex and Antigravity support is experimental and not yet checked in a real session.
What happens to a call that needs approval and nobody answers?
It is denied after the timeout, which is 50 seconds by default.
Does it need a server or daemon?
No. The README says there is no daemon and no network listener, and a SQLite file is the only shared state.
Is Derbent free?
Yes. Derbent is open source, so you can use and self-host it for free.
What are the best alternatives to Derbent?
The closest alternatives to Derbent are Protect MCP, mcpcut, agent-custody, Meandr and agentbelt.
Where this comes from
- Description: written from the project's README and its MCP Registry entry.