Deadzone
io.github.laradji/deadzone
Local-first MCP server: semantic search over library docs. No cloud, no API key, no telemetry.
Install surfaces
How Deadzone runs, per the official MCP registry entry.
- oci
ghcr.io/laradji/deadzone:v0.7.4
Governed execution
How KLA gates calls to Deadzone once it is connected.
A published policy defines which Deadzone actions an agent may take and under what conditions. Each call passes through a policy gate at the tool-call boundary. Permitted actions execute, with the policy basis recorded. Flagged actions execute and are sampled for scheduled human review. High-stakes actions pause and route to a named reviewer on the Decision Desk. The call, the policy decision, and any approval are sealed as an evidence record.
KLA also governs the agent frameworks and model providers you already run. See integrations.