run_npm_command · Project Creator MCP: Risk & Policy

WHAT IT DOES

What run_npm_command does on Project Creator MCP

AI agents invoke run_npm_command to trigger actions in Project Creator 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.

WHY IT NEEDS A POLICY

Why run_npm_command needs a policy

This tool executes npm commands, which are external operations whose effects depend on arguments. npm can run arbitrary scripts, install/modify dependencies, and trigger potentially harmful lifecycle hooks. While not inherently destructive (npm doesn't delete data by default), it is Execute-category because it triggers external operations with effects dependent on the command arguments.

From the tool's definition Tool name 'run_npm_command' indicates execution of npm commands; server description states 'command execution capabilities'; npm commands can execute arbitrary scripts, install packages with side effects, and trigger lifecycle hooks.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

run_npm_command Rate-limited

run_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.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "run_npm_command": {
      "limits": [
        {
          "counter": "run_npm_command_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Project Creator MCP, so you can run agents against it safely.

FAQ

Questions about run_npm_command

What does the run_npm_command tool do? +

run_npm_command. It is categorised as a Execute tool in the Project Creator MCP MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on run_npm_command? +

Register the Project Creator MCP server in PolicyLayer and add a rule for run_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 Project Creator MCP. Nothing to install.

What risk level is run_npm_command? +

run_npm_command is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit run_npm_command? +

Yes. Add a rate_limit block to the run_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.

How do I block run_npm_command completely? +

Set action: deny in the PolicyLayer policy for run_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.

What MCP server provides run_npm_command? +

run_npm_command is provided by the Project Creator MCP server (jackalterman/project-creator-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.