web_install_dependencies · PC-Control MCP Server MCP

WHAT IT DOES

What web_install_dependencies does on PC-Control MCP Server

AI agents invoke web_install_dependencies to trigger actions in PC-Control MCP Server. 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 web_install_dependencies needs a policy

Installing dependencies executes package manager commands on the system, which can run arbitrary scripts (e.g., postinstall hooks), download and execute remote code, and modify the filesystem. This is an Execute-category action with high severity because malicious or compromised packages could lead to code execution. It sits above Write because package install scripts actively run code, not just write files.

From the tool's definition 'Install dependencies for the current project' — triggers an external package installation operation (e.g., npm install, pip install) that runs shell-level commands and modifies the filesystem

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

web_install_dependencies Rate-limited

web_install_dependencies 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": {
    "web_install_dependencies": {
      "limits": [
        {
          "counter": "web_install_dependencies_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 PC-Control MCP Server, so you can run agents against it safely.

FAQ

Questions about web_install_dependencies

What does the web_install_dependencies tool do? +

Install dependencies for the current project. It is categorised as a Execute tool in the PC-Control MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on web_install_dependencies? +

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

What risk level is web_install_dependencies? +

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

Can I rate-limit web_install_dependencies? +

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

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

web_install_dependencies is provided by the PC-Control MCP Server MCP server (krsnmlna1/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.