Run the npm binary with the session-active (or a specified) NVM version.
AI agents invoke npm_run to trigger actions in NVM 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.
This tool allows execution of npm commands, which can run arbitrary JavaScript code through npm scripts, install dependencies with pre/post-install hooks that execute code, and trigger other side effects. The effects depend on the arguments passed (which npm command, which script, what package.json exists).
From the tool's definition Tool description states it 'Run[s] the `npm` binary' with a specified Node version. npm is a package manager that executes arbitrary scripts defined in package.json files (via 'npm run' commands, install hooks, lifecycle scripts, etc.).
Attacks that exploit this kind of access
Run the npm binary with the session-active (or a specified) NVM version. It is categorised as a Execute tool in the NVM MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the NVM MCP Server MCP server in PolicyLayer and add a rule for npm_run: 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 NVM MCP Server. Nothing to install.
npm_run 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_run 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_run. 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_run is provided by the NVM MCP Server MCP server (realjacoblinder/nvm-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →