About this integration
Three-layer firewall for MCP: content, egress and action policy. Proxy or server.
- Transport
- stdio
- Authentication
- none
- Initial setup
- none
- Runtime
- unattended
- Evidence
- documented
- Version
- 0.3.0
- Package
- mcp-output-firewall
- Last compatibility test
- Not independently tested
Connect your agent
mcp-output-firewallThe standalone local server requires no account. Publisher documentation explicitly describes limitations and lack of an independent audit. Not runtime tested.
Capabilities: Scan tool output, Evaluate tool calls, Apply egress and action policy
Connected profiles
Additional details
io.github.tangfei7777-cell/mcp-output-firewall
Source ↗ · Checked 2026-09-170.3.0
Source ↗ · Checked 2026-09-17CC0-1.0; package licenses are separate
Source ↗ · Checked 2026-09-17npm
Source ↗ · Checked 2026-09-17mcp-output-firewall
Source ↗ · Checked 2026-09-200.3.0
Source ↗ · Checked 2026-09-20Publisher documentation defines a client-managed local MCP process and the selected transport; this was documentation-reviewed, not executed.
Source ↗ · Checked 2026-09-20The standalone local server requires no account. Publisher documentation explicitly describes limitations and lack of an independent audit.
Source ↗ · Checked 2026-09-20Use the publisher's pinned README command/configuration for the npm executable; no package or endpoint was executed.
Source ↗ · Checked 2026-09-20Publisher documentation reviewed; package and integration endpoint not executed or independently security-audited.
Source ↗ · Checked 2026-09-20