gradle-build

What gradle-build does on Docker

AI agents invoke gradle-build to trigger actions in Docker. 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 gradle-build is rated High

This tool executes external code (Gradle build scripts) whose effects depend on the build configuration and tasks invoked. While not explicitly destructive in name, Gradle builds can have side effects like downloading dependencies, compiling code, running tests, and executing arbitrary plugins. The incomplete description ('Runs') suggests it triggers a build process.

From the tool's definition Tool name 'gradle-build' and description 'Runs' indicate execution of a build process. Gradle is a build automation tool that compiles code, runs tests, and executes arbitrary tasks defined in build scripts.

The rule that runs gradle-build safely

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

{
  "version": "1",
  "default": "deny",
  "tools": {
    "gradle-build": {
      "limits": [
        {
          "counter": "gradle-build_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

Questions about gradle-build