Baseline MCP tools, enforce role-aware policy, quarantine risky drift, scan responses, and produce audit evidence your security team can inspect.
Built for teams deploying AI agents with MCP tool access
Interlock is an MCP security control plane for teams using multiple MCP servers and agent tools together. It gives operators one place for tool baselines, drift detection, role-aware policy, response scanning, and structured audit logs across heterogeneous servers. This is not a replacement for server RBAC; it is the centralized policy, audit, and output-scanning layer in front of many MCP servers.
Every MCP tool call passes through Interlock — classified, checked against policy, scanned, and logged before reaching upstream tools.
Every request can run layered checks across fingerprints, rules, patterns, LLM judgment, and custom policy.
Interlock intercepts every tool call before it fires. Role-based policies determine whether to allow, monitor, quarantine, or block — based on the request content, user role, and tool sensitivity.
READ MOREComplete feed of every allow, block, monitor, and quarantine decision. Full decision context stored. Export to Datadog, Splunk, Elastic, Slack, PagerDuty, or webhook. Built for teams that need clear evidence for security review, compliance workflows, and incident response.
READ MOREInterlock baselines every MCP tool at discovery time. If schema, capability, or metadata changes later, the drift is classified and can be monitored, denied, or quarantined before execution.
Deploy in the cloud, your VPC, on-premises, or fully air-gapped. You control where your data lives and how it's secured. No vendor lock-in.
Tool and model responses are scanned for injected instructions, secrets, PII, and exfiltration patterns before they are forwarded downstream.
Choose fail-open, fail-closed, or fail-open-safe per environment. If Interlock is unreachable, requests follow your configured policy instead of an implicit default.
Interlock's demo is built around evidence, not a slide deck: run a request through the gateway, watch risky tool behavior get blocked or quarantined, and open the audit trail that explains the decision.
Point an existing SDK client at Interlock and keep provider keys on the gateway host instead of inside every agent app.
Evaluate prompt injection, risky tool arguments, role permissions, and MCP server trust before the call reaches Slack, files, databases, or APIs.
Compare tool schemas against approved baselines, flag new capabilities, and require an operator decision for high-risk changes.
Show allow, block, monitor, and quarantine decisions with reason, severity, role, target, scan time, and export-ready context.
Pre-release. Working with a small group of teams to validate real MCP security workflows.