AAK-RUGPULL-002: New tool added since last pin
- Severity
- HIGH
- Category
- Tool Poisoning (
tool-poisoning) - Scanner
agent_audit_kit/scanners/pin_drift.py- Auto-fixable
- No.
- SARIF name
NewToolSincePin
What it detects
A new tool was added to an MCP server since the last pin. New tools should be reviewed before approval. The Deadbugz campaign (September 2026) added capability after approval rather than at install time, which is why the comparison has to run again after the server is already trusted.
How to fix
Review the new tool's definition and permissions. If it is expected, run agent-audit-kit pin . to record it in .agent-audit-kit/tool-pins.json; if not, delete its entry from the server's tools list. Pinning records every current tool, so deal with any other drift findings first.
To confirm the finding is gone, report only this rule:
agent-audit-kit scan . --rules AAK-RUGPULL-002
Limitations
Counts only tools declared in a server's tools array in a config file. A server added with just a command, whose tools arrive at run time through tools/list, adds no pinned tool, and neither does a tool listed under toolDescriptions, so a new server or a new tool of those shapes is not reported here. A pin file over 1 MB, or one nested past 500 levels, is not read: the scan reports it as incomplete and compares nothing.
References
- OWASP MCP Top 10: MCP03:2025 (Tool Poisoning)
- OWASP Agentic Top 10: ASI02 (Tool Misuse and Exploitation), ASI04 (Agentic Supply Chain Vulnerabilities)
- Adversa AI MCP Top 25 (AAK-defined ids): ADV-RUGPULL-02 (New Tool Added)
- Incidents and advisories: DEADBUGZ-2026-09
All rules. This page is generated from the rule registry when the documentation is built; to change it, change the rule in agent_audit_kit/rules/builtin.py. To give the rule a hand-written write-up, add docs/rules/AAK-RUGPULL-002.md: the page then shows that text, with the registry reference appended under it.