AI agents invoke run_npm to trigger actions in Pentester-MCP. 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.
npm commands execute code—installing packages, running scripts, or executing arbitrary Node.js. On a penetration testing server designed for autonomous tool execution, this capability poses high risk if an AI agent misuses it (e.g., installing malicious packages, running unvetted scripts). The empty description lowers confidence slightly, but the context and naming strongly indicate code execution.
From the tool's definition Tool named 'run_npm' with empty description on Pentester-MCP server that executes over 200 penetration testing tools. The 'run_' prefix combined with 'npm' indicates execution of Node Package Manager commands, which can run arbitrary code.
Documented attack patterns abuse exactly the kind of access run_npm gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Pentester-MCP, and nothing reaches the server without passing your rules. This is the rule we recommend for run_npm:
{
"version": "1",
"default": "deny",
"tools": {
"run_npm": {
"limits": [
{
"counter": "run_npm_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
}run_npm 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.
run_npm. It is categorised as a Execute tool in the Pentester-MCP MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Pentester- MCP server in PolicyLayer and add a rule for run_npm: 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 Pentester-MCP. Nothing to install.
run_npm 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 run_npm 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 run_npm. 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.
run_npm is provided by the Pentester- MCP server (halilkirazkaya/pentester-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Pentester-MCP, 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.
337 Pentester-MCP tools catalogued and risk-classified — across an index of 43,000+ MCP servers.