install

What install does on Build

AI agents invoke install to trigger actions in Build. 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 install is rated High

The tool name 'install' and the context of a build tool server strongly suggest it runs package or dependency installation commands. The description is truncated ('Runs' with no further detail), but given the server's purpose and sibling tools (add-package, audit, ansible-galaxy), this tool likely executes an install command (e.g., npm install, pip install).

From the tool's definition Tool name: 'install'; server description mentions running build tools and commands as typed JSON diagnostics; sibling tools include 'ansible-playbook', 'bazel', suggesting execution of system-level operations

The rule that runs install safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Build, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For install, this is the rule to start with:

{
  "version": "1",
  "default": "deny",
  "tools": {
    "install": {
      "limits": [
        {
          "counter": "install_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

Questions about install