Planlock
github.com/josephcurwin/planlock- Category
- Cybersecurity
- Rank
- No. 4584Tools index
Previous survey · No. 4145 ·
- Pricing
- Open Source
- Type
- TOOL
- Use case
- Security & Identity
- Interfaces
- MCP
- GitHub
- 1 stars
- Date
About
Planlock is an MCP proxy that sits between an AI agent and its tools. The user approves the agent's multi-step plan once, and the proxy then lets through only the calls that plan allows. This avoids both per-call permission prompts that users stop reading and unattended runs with full access.
At a glance
Planlock checks MCP tool calls against a plan you approved in advance. It is worth evaluating if you want an agent to finish a short sequence without approving each call while still enforcing specific arguments and order.
Good fit
Teams that can put the relevant MCP tools behind one gateway and define narrow rules for each step.
Consider something else when
Use other controls for tools or credentials the agent can reach directly outside the gateway.
Start here
Use the project’s mock refund workflow. Verify that it allows the approved amount and blocks a higher amount, a different order and an out-of-order step.
Cost and requirements
The documented example uses Node 20 or newer, Docker and a Windmill MCP server. Approver credentials must stay separate from the agent.
Limits to know
Planlock can constrain calls it sees. It cannot enforce a plan on another route or guarantee a downstream tool behaves as expected.
Sources checked 2026-11-05. Source-based assessment.
Tags
Tech Stack
Comments (0)
No comments yet
Editorially curated, with community endorsements as a secondary signal. Corrections welcome.