High Risk →

nvm

Manages Node.js versions via nvm.

How to control nvm ↓

What nvm does on Http

AI agents invoke nvm to trigger actions in Http. 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.

High Risk

Why nvm needs a policy

Managing Node.js versions via nvm involves executing shell-level version management commands (install, use, alias, uninstall), which can alter the runtime environment, switch active Node.js versions, install or remove binaries, and affect all subsequent code execution.

From the tool's definition "Manages Node.js versions via nvm"

Documented attack patterns abuse exactly the kind of access nvm gives an agent:

How to control nvm

PolicyLayer is an MCP gateway — it sits between your AI agents and Http, and nothing reaches the server without passing your rules. This is the rule we recommend for nvm:

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "nvm": {
      "limits": [
        {
          "counter": "nvm_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

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

  1. Create a free account and register Http — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
RATE-LIMIT THIS TOOL →

Free to start. No card required.

Related tools and policies

Go deeper

Questions about nvm

What does the nvm tool do? +

Manages Node.js versions via nvm. It is categorised as a Execute tool in the Http 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? +

Register the Http MCP server in PolicyLayer and add a rule for nvm: 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 Http. Nothing to install.

What risk level is nvm? +

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

Can I rate-limit nvm? +

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

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

nvm is provided by the Http MCP server (@paretools/http). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Http tool call.

Start from Http, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

Free to start. No card required.

202 Http tools catalogued and risk-classified — across an index of 43,000+ MCP servers.

// GET IN TOUCH

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

Message sent.

We'll get back to you soon.