Ejecutar un script definido en package.json
AI agents invoke npm_run_script to trigger actions in NPM 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 triggers execution of user-defined scripts from package.json, which can run arbitrary shell commands and external processes. While the scripts themselves are pre-defined in the project, an AI agent with access to this tool could execute malicious scripts or scripts with unintended side effects.
From the tool's definition Tool name 'npm_run_script' combined with description 'Ejecutar un script definido en package.json' (Execute a script defined in package.json) directly indicates execution of arbitrary scripts.
Attacks that exploit this kind of access
Ejecutar un script definido en package.json. It is categorised as a Execute tool in the NPM MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the NPM MCP Server MCP server in PolicyLayer and add a rule for npm_run_script: 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 NPM MCP Server. Nothing to install.
npm_run_script 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_script 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_script. 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_script is provided by the NPM MCP Server MCP server (kpangaa/npm-mcp-server). 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 →