npm_command
Run npm commands (install, test, build, etc)
This record as markdown: /tools/agentics-ai-code-mcp/npm-command.md
What npm_command does on Code MCP Server
AI agents invoke npm_command to trigger actions in Code 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.
Why npm_command is rated High
npm commands trigger external operations whose effects depend on arguments. While 'test' and 'build' are relatively contained, 'install' modifies the project state by downloading and integrating dependencies. More critically, npm scripts can execute arbitrary shell commands defined in package.json, making this a code execution tool.
From the tool's definition Tool description states 'Run npm commands' which are executable operations. npm commands can install packages (modifying dependencies), run scripts (arbitrary code execution), and build projects.
Attacks that exploit this kind of access
The rule that runs npm_command safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Code MCP Server, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For npm_command, this is the rule to start with:
npm_command 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.
The button opens the PolicyLayer dashboard: create your workspace, connect Code MCP Server, apply this rule, and every npm_command call is checked against it from then on.
Questions about npm_command
Run npm commands (install, test, build, etc). It is categorised as a Execute tool in the Code MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Code MCP Server MCP server in PolicyLayer and add a rule for npm_command: 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 Code MCP Server. Nothing to install.
npm_command 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_command 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_command. 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_command is provided by the Code MCP Server MCP server (agentics-ai/code-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Code MCP Server, and thousands of servers like it.
Across the catalogue