Threat Rules

@guardbee/mcp-threat-rules

🇬🇧 English | 🇹🇷 Türkçe | 🇨🇳 中文 | 🇯🇵 日本語 | 🇰🇷 한국어 | 🇧🇷 Português | 🇪🇸 Español | 🇩🇪 Deutsch

[npm version] [npm downloads] [License: MIT]

GuardBee MCP bridge to Agent Threat Rules (ATR) — the open, Sigma-like detection standard for AI agent threats (prompt injection, tool poisoning, context exfiltration, MCP attacks).

ATR evaluates runtime events. GuardBee’s other packages mostly scan source/catalogs. This package connects both: run ATR plus GuardBee rules (KVKK / Turkish & Chinese injection / Chinese ID / lethal-trifecta intent), then jump to the matching GuardBee auditor.

Custom project rules: drop YAML into .guardbee/atr-rules/ or set GUARDBEE_ATR_RULES_DIR.

Telemetry is off by default. With GUARDBEE_TELEMETRY=1 it sends the server, tool, success, duration and short parameter values such as a file path; longer strings and fields like content, token or password are replaced with a placeholder. See @guardbee/mcp-telemetry.

Claude ──► threat-rules (ATR) ──► matches + GuardBee follow-up hints              │              ├─ evaluate_text / evaluate_file / evaluate_event              ├─ list_rules / rule_stats              └─ explain_bridge

Built-in GuardBee rules include KVKK TC Kimlik, Turkish & Chinese injection, Chinese national ID, and lethal-trifecta intent (GB-ATR-2026-00001 … 00005).

Upstream ATR is MIT-licensed and already used across the industry. We depend on agent-threat-rules rather than forking it.

Tools

CLI

npx @guardbee/mcp-threat-rules eval "…" --format=json --fail-on=highnpx @guardbee/mcp-threat-rules scan ./prompt.txt --format=sarifnpx @guardbee/mcp-threat-rules list --source=guardbeenpx @guardbee/mcp-threat-rules stats

Related GuardBee packages

Feedback

Questions, ideas, or a false positive? Start a thread in GitHub Discussions or open an issue. If GuardBee is useful to you, a ⭐ on the repository helps others find it.