package_install · Universal Dev MCP: Risk & Policy

WHAT IT DOES

What package_install does on Universal Dev MCP

AI agents invoke package_install to trigger actions in Universal Dev MCP. 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 package_install needs a policy

This tool installs packages using pip, npm, or composer depending on the detected environment. Installing packages executes external processes that modify the system environment, can introduce malicious dependencies, and has side effects beyond simple data writes.

From the tool's definition Package install karna (auto-detect: pip/npm/composer)

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

package_install Rate-limited

package_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": {
    "package_install": {
      "limits": [
        {
          "counter": "package_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 Universal Dev MCP, so you can run agents against it safely.

FAQ

Questions about package_install

What does the package_install tool do? +

Package install karna (auto-detect: pip/npm/composer). It is categorised as a Execute tool in the Universal Dev MCP MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on package_install? +

Register the Universal Dev MCP server in PolicyLayer and add a rule for package_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 Universal Dev MCP. Nothing to install.

What risk level is package_install? +

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

Can I rate-limit package_install? +

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

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

package_install is provided by the Universal Dev MCP server (kallusuvaidyam/universal_mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.