gem-install

What gem-install does on Build

AI agents invoke gem-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 gem-install is rated High

Installing a Ruby gem executes an external package manager command that downloads and installs third-party code onto the system. This is Execute category because it triggers an external operation (gem installation) whose effects depend on arguments (which gem and version). Severity is high because a misused gem-install could install malicious packages, introduce vulnerabilities, or compromise the system environment.

From the tool's definition 'gem-install' - installs a Ruby gem, which executes package installation commands that modify the system environment by downloading and installing third-party code

The rule that runs gem-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 gem-install, this is the rule to start with:

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

Questions about gem-install