Skip to content

AAK-MCP-007: MCP server lacks version pinning in args

Severity
LOW
Category
MCP Configuration (mcp-config)
Scanner
agent_audit_kit/scanners/mcp_config.py
Auto-fixable
No.
SARIF name
McpUnpinnedPackageVersion

What it detects

Package name in args lacks @version suffix when using npx/uvx. Unpinned packages can silently update to malicious versions. Not reported for a launch AAK-SUPPLY-001 reports in the same scan.

How to fix

Pin with an exact @x.y.z suffix, for example npx -y some-mcp-server@1.4.2. The four npm reference servers (@modelcontextprotocol/server-filesystem, -memory, -everything and -sequential-thinking) left their date-based releases for semantic versioning in October 2026, so pin a SemVer release of them, never a 2025.x or 2026.x one. A launcher pin fixes only the top-level package; a lockfile install or an image digest fixes the whole tree. The launch arguments are part of what was reviewed too: mongodb-mcp-server serves different tools with and without --readOnly.

To confirm the finding is gone, report only this rule:

agent-audit-kit scan . --rules AAK-MCP-007

Limitations

Looks for a package argument after npx, uvx, bunx or pnpx that has no @version suffix. Any suffix counts as a pin, including the floating tag @latest. The same package fetched through cmd /c npx is not checked.

References

  • OWASP MCP Top 10: MCP04:2025 (Software Supply Chain Attacks & Dependency Tampering)
  • OWASP Agentic Top 10: ASI04 (Agentic Supply Chain Vulnerabilities)
  • Adversa AI MCP Top 25 (AAK-defined ids): ADV-SUPPLY-02 (Unpinned Package)

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-MCP-007.md: the page then shows that text, with the registry reference appended under it.