WARDEN — MCP Security Firewall
io-github-alexar76-warden declares 9 capabilities across 9 tools, with 2 critical issues.
Issues
9 of 9 tools declare no way for the customer to switch them off once granted. This applies to every tool because MCP has no field in which to declare a revocation mechanism; the product may provide one outside MCP that a manifest cannot show.
2 tools are classified as irreversible and declare no limit.
9 of 9 tools declare no expiry. This applies to every tool because MCP has no field in which to declare an expiry; the product may provide one outside MCP that a manifest cannot show.
9 of 9 tools declare no record of their actions that the customer can read. This applies to every tool because MCP has no field in which to declare an audit requirement; the product may provide one outside MCP that a manifest cannot show.
7 tools can read data and declare no limit.
Declared capabilities
| Tool | Read as | Basis |
|---|---|---|
vet_mcp_server | read |
declared |
static_scan_tools | read |
declared |
classify_sensitive_tools | read |
declared |
check_egress_url | read |
declared |
canonicalize_json | read |
declared |
list_scan_rules | read |
declared |
status_mcp_server | read |
declared |
approve_mcp_server | destructive |
declared |
revoke_mcp_server | destructive |
declared |
Record history
| Recorded | Exposure | Source |
|---|---|---|
| 2026-10-14 | 40 | tools/list answered by the npm package @aimarket/warden@0.16.0 (published to npm as @aimarket/warden, listed in the official MCP registry as io.github.alexar76/warden 0.16.0), run in an isolated container with no network access and no credentials |
tools/list response and it will be re-scored and dated.
Corrections are published alongside the original, not in place of it.