adb_gradle

What adb_gradle does on Deepadb

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

Gradle tasks can execute arbitrary code during the build process, including custom plugins, shell commands, and side effects that depend on the task arguments. This falls squarely into Execute rather than Write because the effects are not limited to reversible data modifications—Gradle can invoke compilers, run tests, download dependencies, and trigger external systems.

From the tool's definition Tool name 'adb_gradle' and description 'Run a Gradle task in an Android project directory' indicate execution of arbitrary Gradle build tasks, which can compile code, run tests, execute plugins, and trigger external operations.

The rule that runs adb_gradle safely

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

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

Questions about adb_gradle