add-package
Runs dotnet add package to add a NuGet package and returns structured results. WARNING: may execute untrusted code.
This record as markdown: /tools/io-github-dave-london-github/add-package.md
What add-package does on Github
AI agents invoke add-package to trigger actions in Github. 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 add-package is rated High
This tool executes a dotnet CLI command to add a NuGet package. The explicit warning about executing untrusted code elevates the risk significantly — NuGet package installation can trigger build scripts and arbitrary code execution. This is an Execute-category action with high severity due to the potential for supply chain attacks and arbitrary code execution.
From the tool's definition 'Runs dotnet add package' and 'WARNING: may execute untrusted code'
Attacks that exploit this kind of access
The rule that runs add-package safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Github, 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 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.
The button opens the PolicyLayer dashboard: create your workspace, connect Github, apply this rule, and every add-package call is checked against it from then on.
Questions about add-package
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 Github MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Github 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 Github. Nothing to install.
add-package is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
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.
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.
add-package is provided by the Github MCP server (@paretools/github). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Github, and thousands of servers like it.
Across the catalogue