nvm_install · NVM MCP Server MCP: Risk & Policy

WHAT IT DOES

What nvm_install does on NVM MCP Server

AI agents invoke nvm_install 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.

WHY IT NEEDS A POLICY

Why nvm_install needs a policy

Installing a Node.js version triggers an external operation that downloads and installs software onto the system. This is more than a simple write — it executes NVM commands and modifies the system environment by adding a new Node.js runtime. The blast radius is medium as it could install unexpected or malicious Node versions if misused.

From the tool's definition Install a Node.js version using NVM

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

nvm_install Rate-limited

nvm_install 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": {
    "nvm_install": {
      "limits": [
        {
          "counter": "nvm_install_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 NVM MCP Server, so you can run agents against it safely.

FAQ

Questions about nvm_install

What does the nvm_install tool do? +

Install a Node.js version using NVM. 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.

How do I enforce a policy on nvm_install? +

Register the NVM MCP Server MCP server in PolicyLayer and add a rule for nvm_install: 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.

What risk level is nvm_install? +

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

Can I rate-limit nvm_install? +

Yes. Add a rate_limit block to the nvm_install 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 nvm_install completely? +

Set action: deny in the PolicyLayer policy for nvm_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 nvm_install? +

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