add-package

Runs dotnet add package to add a NuGet package and returns structured results. WARNING: may execute untrusted code.

SERVERNpm SOURCEDave-London/Pare

High RISK CLASS

Category Execute

Parameters 00 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/io-github-dave-london-npm/add-package.md

WHAT IT DOES

What add-package does on Npm

AI agents invoke add-package to trigger actions in Npm. 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.

RISK

Why add-package is rated High

This tool executes a dotnet CLI command to add a NuGet package, which involves running external package manager code that may include install scripts or other executable content. The explicit warning about untrusted code execution elevates the severity. While it primarily modifies project files (Write), the potential for arbitrary code execution during package installation makes Execute the appropriate category.

From the tool's definition 'Runs dotnet add package' and 'WARNING: may execute untrusted code'

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs add-package safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Npm, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For add-package, this is the rule to start with:

add-package Rate-limited

add-package 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": {
    "add-package": {
      "limits": [
        {
          "counter": "add-package_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Npm, apply this rule, and every add-package call is checked against it from then on.

FAQ

Questions about add-package

What does the add-package tool do? +

Runs dotnet add package to add a NuGet package and returns structured results. WARNING: may execute untrusted code. It is categorised as a Execute tool in the Npm MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on add-package? +

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

What risk level is add-package? +

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

Can I rate-limit add-package? +

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

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

add-package is provided by the Npm MCP server (Dave-London/Pare). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Npm, and thousands of servers like it.

This server

All 202 Npm tools → High-risk tools on this server →

Across the catalogue

All high-risk MCP tools → The MCP Attack Database →

Guides

Govern code and CI agents →Agent sandbox →Least privilege for MCP →