project_install_deps · LocalAnt MCP: Risk & Policy

WHAT IT DOES

What project_install_deps does on LocalAnt

AI agents invoke project_install_deps to trigger actions in LocalAnt. 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 project_install_deps needs a policy

Installing dependencies executes package manager commands (npm install, pip install, etc.) on the host system, which runs external code and can introduce arbitrary packages/scripts. This is an Execute-level operation with high severity because a misused or compromised dependency installation can execute malicious code, modify system state, and have wide blast radius.

From the tool's definition Install project dependencies using the detected package manager

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

project_install_deps Rate-limited

project_install_deps 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": {
    "project_install_deps": {
      "limits": [
        {
          "counter": "project_install_deps_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 LocalAnt, so you can run agents against it safely.

FAQ

Questions about project_install_deps

What does the project_install_deps tool do? +

Install project dependencies using the detected package manager. It is categorised as a Execute tool in the LocalAnt MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on project_install_deps? +

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

What risk level is project_install_deps? +

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

Can I rate-limit project_install_deps? +

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

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

project_install_deps is provided by the LocalAnt MCP server (yuga-hashimoto/localant). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.