Runs dotnet add package to add a NuGet package and returns structured results. WARNING: may execute untrusted code.
AI agents invoke add-package to trigger actions in Make. 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.
This tool executes a dotnet CLI command to add a NuGet package, which runs external tooling and may fetch and execute untrusted code from package registries. The explicit warning about untrusted code execution elevates this beyond a simple Write operation.
From the tool's definition 'Runs dotnet add package' and 'WARNING: may execute untrusted code'
Documented attack patterns abuse exactly the kind of access add-package gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Make, and nothing reaches the server without passing your rules. This is the rule we recommend for add-package:
{
"version": "1",
"default": "deny",
"tools": {
"add-package": {
"limits": [
{
"counter": "add-package_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
}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.
Free to start. No card required.
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 Make MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Make 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 Make. 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 Make MCP server (Dave-London/Pare). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Make, 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 Make tools catalogued and risk-classified — across an index of 43,000+ MCP servers.