Interlock seeks MCP builders to test runtime tool-drift detection
u/Temporary_Bar9501 is recruiting 2–3 design partners to test Interlock, an open-source MCP runtime trust layer that detects post-approval tool drift and quarantines risky schema or behavior changes before execution.
Score breakdown
The post highlights a concrete security gap in MCP agent workflows — that a one-time tool approval does not account for subsequent changes to a tool's capability surface — and presents Interlock as an open-source mechanism to detect and quarantine such drift before execution.
- 01Interlock is an open-source MCP runtime trust layer built by u/Temporary_Bar9501.
- 02The core problem it targets is tool drift: an approved MCP tool can later change its schema, data access, auth scope, side effects, or behavior without the agent's knowledge.
- 03Features include drift detection, hold/quarantine of risky changes before execution, audit evidence called 'Security Receipts', and a shadow mode for safer testing.
u/Temporary_Bar9501 posted to r/mcp seeking 2–3 design partners to test Interlock, a self-described open-source MCP runtime trust layer. The project targets a specific gap in how AI agents handle tool trust: an MCP tool can be approved once and then silently evolve — changing its schema, data access patterns, external reach, side effects, or auth scope — while the agent continues to treat it as trusted. Interlock is built to close that gap by establishing a baseline of an approved tool's capability surface and continuously monitoring for drift after approval.
The project is hosted on GitHub at `github.com/MaazAhmed47/Interlock` and has a demo available on YouTube, with a project site at `getinterlock.dev`.
The tool's feature set includes post-approval drift detection, a hold/quarantine mechanism to block risky changes before they execute, audit evidence stored as "Security Receipts," and a shadow mode intended to support safer testing without live destructive workflows. The project is hosted on GitHub at `github.com/MaazAhmed47/Interlock` and has a demo available on YouTube, with a project site at `getinterlock.dev`.
The ideal design partners described in the post are MCP server maintainers, AI-agent teams using real tools, DevTools and workflow automation builders, and security engineers evaluating MCP risk. The only requirement is a non-production MCP workflow touching APIs, files, databases, GitHub, CI/CD, business tools, or external services — no production credentials or live destructive workflows are involved, and self-hosted or isolated demo setups are acceptable.
Key facts
- 01Interlock is an open-source MCP runtime trust layer built by u/Temporary_Bar9501.
- 02The core problem it targets is tool drift: an approved MCP tool can later change its schema, data access, auth scope, side effects, or behavior without the agent's knowledge.
- 03Features include drift detection, hold/quarantine of risky changes before execution, audit evidence called 'Security Receipts', and a shadow mode for safer testing.
- 04The post seeks 2–3 design partners to test Interlock on one real non-production MCP/agent workflow.
- 05Target testers include MCP server maintainers, AI-agent teams, DevTools builders, and security engineers evaluating MCP risk.
- 06Testing is restricted to non-production workflows — no production credentials or live destructive workflows.
- 07The project is available at github.com/MaazAhmed47/Interlock with a site at getinterlock.dev.
Topics
Summary and scoring are generated automatically from the original article. We always link back to the publisher and never republish images or paywalled content. Last processed Jun 9, 2026 · 17:05 UTC. How this works →