interlock-mcp

# interlock-mcp **A fuse for autonomous agents, over the Model Context Protocol.** A fuse is a deliberately weak link. It costs pennies, it breaks first, and it is the only reason you can run real current through the wire at all. This server gives your agent one: it can ask whether an action is safe *before* taking it, instead of finding out afterwards. ``` agent ──"may I delete prod-orders-db?"──▶ interlock-mcp ◀──"DENY · CATASTROPHIC · irreversible with high data-loss risk"── ``` ## Why you might want it An agent with credentials and a goal will eventually reach for something it should not. Not because it is badly built — because it is optimising to make a problem stop, and the fastest way to stop an error is often a terrible idea. Granting `allUsers` read on a bucket really would silence a lot of 503s. The usual answers are to withhold the capability, or to keep a human watching. The first makes the agent useless for the case you wanted it for; the second means the automation never pays for itself. A fuse is the third answer. ## Install Nothing to configure. No cloud account, no API key, no network. ```jsonc // Claude Desktop ~/Library/Application Support/Claude/claude_desktop_config.json // Claude Code ~/.claude.json Cursor ~/.cursor/mcp.json { "mcpServers": { "interlock": { "command": "uvx", "args": [ "--from", "git+https://github.com/tanwar-div/interlock-agent-control-plane.git#subdirectory=interlock-mcp", "interlock-mcp" ] } } } ``` From a checkout instead: ```bash uv pip install -e ./interlock-mcp interlock-mcp # speaks MCP over stdio ``` ## Tools Every tool is **read-only**. Nothing here changes anything, and that is declared to your client through tool annotations rather than merely promised in prose. ### `score_action` Ask whether one action is safe. Pass the operation and the **exact** arguments — granting a bucket role to one named service accou…