gradle-test

What gradle-test does on Search

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

A tool that runs Gradle tests executes external processes and build system commands. The truncated description begins with 'Runs', confirming execution behavior. Running arbitrary test suites can trigger compilation, code execution, network access, and file system changes, making this an Execute-category tool with high severity due to the broad blast radius of build system execution.

From the tool's definition Tool name 'gradle-test' and server context of 'Structured code search operations (ripgrep + fd)' combined with 'Runs' (truncated description) — 'Runs' indicates execution of Gradle test suite, an external build/test operation.

The rule that runs gradle-test safely

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

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

Questions about gradle-test