Put a permission gate between your agent and its tools

Description and use

DeadBolt adds an admission gate between an LLM agent and its tools, requiring operator approval before execution.

Problem

Agents may attempt actions that users have not authorized, risking unintended tool usage.

Outcome

DeadBolt successfully blocks unauthorized tool calls, requires operator approval, and logs execution outcomes, demonstrating a practical admission gate for LLM agents.

Workflow

• 1. Download DeadBolt MCP bundle and editor_setup.py
• 2. Run editor_setup.py to prepare and verify the bundle
• 3. Install DeadBolt in the editor (Cursor or VS Code)
• 4. Create a disposable demo environment with editor_setup.py demo
• 5. Call demo tools to test allowed, denied, and human‑required actions
• 6. Use operator terminal to approve or revoke actions
• 7. Inspect effects.txt and events.jsonl for evidence of execution or denial

Evidence

A prompt can explain the rules; a dispatcher can enforce them before a connected tool body starts.

Source

I built DeadBolt at NextEleven to provide that local admission point.

Source

The bundle supports Apple Silicon/Intel Macs, Linux x64 with glibc and Windows x64.

Source

The default lease expires after 60 seconds without admission.

Source