Medium Risk

install

Runs npm/pnpm/yarn install and returns a structured summary of added/removed packages and vulnerabilities. Auto-detects package manager via lock files (pnpm-lock.yaml → pnpm, yarn.lock → yarn, otherwise npm). Lifecycle scripts (preinstall/postinstall) are skipped by default for safety. Set ignore...

Accepts file system path (path); High parameter count (15 properties)

Part of the Npm MCP server. Enforce policies on this tool with Intercept, the open-source MCP proxy.

@paretools/npm Write Risk 3/5

AI agents use install to create or modify resources in Npm. Write operations carry medium risk because an autonomous agent could trigger bulk unintended modifications. Rate limits prevent a single agent session from making hundreds of changes in rapid succession. Argument validation ensures the agent passes expected values.

Without a policy, an AI agent could call install repeatedly, creating or modifying resources faster than any human could review. Intercept's rate limiting ensures write operations happen at a controlled pace, and argument validation catches malformed or unexpected inputs before they reach Npm.

Write tools can modify data. A rate limit prevents runaway bulk operations from AI agents.

io-github-dave-london-npm.yaml
tools:
  install:
    rules:
      - action: allow
        rate_limit:
          max: 30
          window: 60

See the full Npm policy for all 10 tools.

Tool Name install
Category Write
MCP Server Npm MCP Server
Risk Level Medium

View all 10 tools →

Agents calling write-class tools like install have been implicated in these attack patterns. Read the full case and prevention policy for each:

Browse the full MCP Attack Database →

Other tools in the Write risk category across the catalogue. The same policy patterns (rate-limit, validate) apply to each.

What does the install tool do? +

Runs npm/pnpm/yarn install and returns a structured summary of added/removed packages and vulnerabilities. Auto-detects package manager via lock files (pnpm-lock.yaml → pnpm, yarn.lock → yarn, otherwise npm). Lifecycle scripts (preinstall/postinstall) are skipped by default for safety. Set ignoreScripts to false if packages need postinstall scripts to work (e.g., esbuild, sharp).. It is categorised as a Write tool in the Npm MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on install? +

Add a rule in your Intercept YAML policy under the tools section for install. You can allow, deny, rate-limit, or validate arguments. Then run Intercept as a proxy in front of the Npm MCP server.

What risk level is install? +

install is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit install? +

Yes. Add a rate_limit block to the install rule in your Intercept 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 install completely? +

Set action: deny in the Intercept policy for install. 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 install? +

install is provided by the Npm MCP server (@paretools/npm). Intercept sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policies on Npm

Open source. One binary. Zero dependencies.

npx -y @policylayer/intercept
github.com/policylayer/intercept →
// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.