Pipelock

data-ai MCP Server

Open-source AI agent firewall for MCP security and agent egress. Scans mediated HTTP, MCP, A2A, and WebSocket traffic for exfiltration, SSRF, and prompt injection, and emits mediator-signed action receipts: verifiable audit evidence from outside the agent.

Verified
data-aidata-ai
6 views720 stars83 forksApache-2.0

Why This Matters

Discovered via github-topic:mcp and last synced 2mo ago.

Verified
Source
github-topic:mcp
Stars
720
Last synced
2mo ago
Install
Check source

Install

Install instructions not detected yet

Check the source repository for the latest setup steps.

View source instructions
15
Tools
0
Resources
0
Prompts
Standard I/O
Transport

Available Tools (15)

balanced

New agents (tuning phase)

Document

What's In It

audit

audit

strict

Uncensored/abliterated models

Threat

Coverage

Pipelock

Scanners (agent-scan)

Unrestricted

Evaluation before enforcement

Mode

Action

File

Mode

Metric

Value

Allowlist-only

None

Strict

Balanced

Feature

What It Does

Yes

No (Python)

Logged

> **Honest assessment:** Strict mode blocks outbound HTTP that traverses Pipelock except allowlisted API domains, so there is no exfiltration channel through the proxy itself. Balanced mode raises the bar from "one curl command" to "sophisticated pre-planned attack." Audit mode gives you visibility you don't have today. With the sandbox enabled (`pipelock sandbox`) or the host/cluster containment topology enforced, pipelock adds an OS or deployment boundary on top of content inspection. Direct egress still has to be blocked by that boundary for non-cooperative tools that ignore proxy settings. ## Configuration Generate a config from one of three CLI presets, or let `pipelock audit` tailor one to your project: ```bash pipelock generate config --preset balanced > pipelock.yaml pipelock audit ./my-project -o pipelock.yaml ```