AI agents invoke npm_audit to trigger actions in SAST MCP Server. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.
Based on the tool name and server context, npm_audit likely runs 'npm audit' against a package or directory to perform dependency vulnerability scanning. This constitutes executing an external command/process. The description is empty, which lowers confidence, but the SAST server context and sibling tools (bandit_scan, bearer_scan, brakeman_scan, etc.) strongly suggest this tool executes a scan command.
From the tool's definition Tool name 'npm_audit' on a SAST server that 'integrates 15+ static application security testing tools' and 'enabling automated vulnerability scanning'; description is empty.
Documented attack patterns abuse exactly the kind of access npm_audit gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and SAST MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for npm_audit:
{
"version": "1",
"default": "deny",
"tools": {
"npm_audit": {
"limits": [
{
"counter": "npm_audit_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
}npm_audit stays usable, but rate-capped — a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.
Free to start. No card required.
npm_audit. It is categorised as a Execute tool in the SAST MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the SAST MCP Server MCP server in PolicyLayer and add a rule for npm_audit: allow, deny, rate-limit, or require approval. Point your MCP client at the PolicyLayer proxy URL and the rule is enforced on every call, before it reaches SAST MCP Server. Nothing to install.
npm_audit is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the npm_audit rule in your PolicyLayer policy. For example, setting max: 10 and window: 60 limits the tool to 10 calls per minute. Rate limits are tracked per agent session and reset automatically.
Set action: deny in the PolicyLayer policy for npm_audit. The AI agent will receive a policy violation error and cannot call the tool. You can also include a reason field to explain why the tool is blocked.
npm_audit is provided by the SAST MCP Server MCP server (sengtocxoen/sast-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from SAST MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
39 SAST MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.