gradle-build

What gradle-build does on Git

AI agents invoke gradle-build to trigger actions in Git. 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 invokes Gradle's build system, which executes arbitrary build scripts, plugins, and external code. The effects depend on build configuration and arguments, making it an Execute category risk. Severity is high because build scripts can spawn processes, modify the file system, make network calls, and affect the development/deployment pipeline.

From the tool's definition Tool name is 'gradle-build' and description states 'Runs' (implying execution of build operations). Gradle is a build automation tool that executes arbitrary code and system commands during builds.

The rule that runs gradle-build safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Git, 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