Index / devtools
io.github.GuardBee/threat-rules
io-github-guardbee-threat-rules declares 7 capabilities across 7 tools, with 1 critical issue.
20/100 exposureModerate
Manifest recorded 2026-10-15 from tools/list answered by the npm package @guardbee/mcp-threat-rules@0.4.2 (published to npm as @guardbee/mcp-threat-rules, listed in the official MCP registry as io.github.GuardBee/threat-rules 0.4.2), run in an isolated container with no network access and no credentials. The date changes only when the manifest does. Not verified by a maintainer.
Issues
These describe what this server's manifest declares. A product can provide controls that MCP has no
way to express — token revocation, an admin console, audit logs — and this page cannot see them. The absence of a
declaration is not evidence that a control is absent.
critical · no-revocation · All 7 tools
7 of 7 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.
high · no-expiry · All 7 tools
7 of 7 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.
high · no-audit-trail · All 7 tools
7 of 7 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.
high · uncapped-write · 2 of 7 tools
2 tools can modify data and declare no limit.
low · uncapped-read · 5 of 7 tools
5 tools can read data and declare no limit.
Declared capabilities
How each tool was read. declared means the server's own annotation said so — self-reported and
unverified. inferred is from the tool's name. assumed means nothing indicated either way.
| Tool | Read as | Basis |
|---|
evaluate_text | write |
assumed |
evaluate_file | read |
inferred |
evaluate_event | write |
assumed |
list_rules | read |
inferred |
rule_stats | read |
inferred |
explain_bridge | read |
inferred |
framework_map | read |
inferred |
Record history
Earlier records for this server. A correction is added here, never written over the record it corrects.
| Recorded | Exposure | Source |
|---|
| 2026-10-14 | 18 |
tools/list answered by the npm package @guardbee/mcp-threat-rules@0.2.1 (published to npm as @guardbee/mcp-threat-rules, listed in the official MCP registry as io.github.GuardBee/threat-rules 0.2.1), run in an isolated container with no network access and no credentials |
Answering this question about your own agent? The self-serve
stack report applies the same reading to your own stack or server and gives you a dated
document you can hand to a customer's security review. It is generated in your browser, with nobody to wait for.
Buying one does not change this page, its score or its place in the index — see
Independence.
Maintain this server? If this page misreads your manifest, or your server has changed,
submit its current tools/list response and it will be re-scored and dated.
Corrections are published alongside the original, not in place of it.