MCP Output Firewall
PulseGate's liveness check found it on 15 Sep 2026; it has been in the index since 15 Sep 2026. How this is checked
MCP Output Firewall is an open-source security layer for Model Context Protocol deployments. It inspects tool output, applies egress policies, and evaluates actions to block prompt injection, tool poisoning, and data exfiltration before they reach an AI agent.
Inferred · not functionally tested
Overview
6 featuresPurpose: Preventing prompt injection, tool poisoning, unauthorized egress, and unsafe actions in MCP-based AI agents.
Inferred · not functionally tested
Audience: AI developers and security engineers building MCP agents
Inferred · not functionally tested
Functions: agents, monitoring
Inferred · not functionally tested
Interfaces: API: indicated (inferred, not tested) · MCP: indicated (inferred, not tested) · CLI: indicated (inferred, not tested) · Self-hosting: indicated (inferred, not tested)
Recorded constraints: pricing: open_source · license: Open Source · platforms: WEB · deployment: browser, self_hosted, cli, api_only
Constraint provenance is unknown; confirm requirements with the publisher.
Record sources: github.com. These links do not verify the individual claims.
In the AI security & guardrails space, MCP Output Firewall takes a focused approach. Inferred · not functionally tested: It focuses on preventing prompt injection, tool poisoning, unauthorized egress, and unsafe actions in MCP-based AI agents. Inferred · not functionally tested: MCP Output Firewall is an open-source project aimed at AI developers and security engineers building MCP agents. Basis unknown · not verified: The project is open source (Open Source). Basis unknown · not verified: It runs on the web, the command line, and API, and it can be self-hosted.
Behind MCP Output Firewall is tangfei7777-cell. Inferred · not functionally tested: Key capabilities include content inspection, egress policies, and action policies. Inferred · not functionally tested: Catalogued interfaces include an MCP server.
Summary written by a language model from the project’s public pages.
Tasks: Inferred · not functionally tested
- Content inspection
- Egress policies
- Action policies
- Prompt injection detection
- Tool poisoning detection
- Exfiltration prevention
Topics: Inferred · not functionally tested
Built with & integrations
Trust & compliance
Indexing history
1What PulseGate has recorded for this listing
- Indexed15 Sep · 14:49 UTCMCP Output Firewall seen via MCP Registry (official)Source: MCP Registry (official) · Open
Frequently asked questions about MCP Output Firewall
- What is MCP Output Firewall?
- Inferred · not functionally tested: MCP Output Firewall focuses on preventing prompt injection, tool poisoning, unauthorized egress, and unsafe actions in MCP-based AI agents. It is catalogued under AI security & guardrails on PulseGate.
- Who is MCP Output Firewall for?
- Inferred · not functionally tested: MCP Output Firewall is an open-source project built for AI developers and security engineers building MCP agents.
- Does MCP Output Firewall have a free plan?
- Basis unknown · not verified: Yes — MCP Output Firewall is open source under the Open Source license and free to use.
- What platforms does MCP Output Firewall run on?
- Basis unknown · not verified: MCP Output Firewall runs on the web, the command line, and API. It can also be self-hosted.
- Is MCP Output Firewall still active?
- PulseGate's liveness check found it on 15 Sep 2026.
- What are alternatives to MCP Output Firewall?
- Similar projects tracked by PulseGate include ai-firewall-mcp, agent-prompt-injection-firewall-mcp, and cheetah-firewall-mcp.ai-firewall-mcpagent-prompt-injection-firewall-mcpcheetah-firewall-mcp
- Who makes MCP Output Firewall?
- MCP Output Firewall is developed by tangfei7777-cell.
- Is MCP Output Firewall open source?
- Basis unknown · not verified: Yes — MCP Output Firewall is open source under the Open Source license.
Similar projects
Closest matches by what these projects do