gradle_build

What gradle_build does on Yaver

AI agents invoke gradle_build to trigger actions in Yaver. 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.

Parameters from the server's own tool schema.

Why gradle_build is rated High

Gradle build tasks execute arbitrary build logic and can invoke shell commands, download dependencies, run custom scripts, and trigger side effects beyond simple compilation. The tool's capability to 'run' a build task makes it an Execute category risk. Severity is high because misuse could compromise the build pipeline, inject malicious code during compilation, or trigger unintended deployments.

From the tool's definition Tool description states 'Run a Gradle build task', which is direct code execution in a build system that can trigger arbitrary scripts, compilations, and potentially invoke external processes or system commands during the build lifecycle.

Risk signalsAccepts file system path (directory)

The rule that runs gradle_build safely

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