AI agents invoke gradle-build to trigger actions in Test. 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.
This tool triggers external build operations through Gradle, which can execute arbitrary code and scripts. While not immediately destructive, it has high blast radius as builds can modify the filesystem, download dependencies, and execute arbitrary tasks.
From the tool's definition Tool name 'gradle-build' and description 'Runs' indicates execution of build commands. Gradle is a build automation tool that executes arbitrary code during the build process, including compilation, testing, and plugin execution whose effects depend on build…
Attacks that exploit this kind of access
Runs. It is categorised as a Execute tool in the Test MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Test MCP server in PolicyLayer and add a rule for gradle-build: allow, deny, rate-limit, or require approval. Point your MCP client at the PolicyLayer proxy URL and the rule is enforced on every call, before it reaches Test. Nothing to install.
gradle-build is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the gradle-build rule in your PolicyLayer policy. For example, setting max: 10 and window: 60 limits the tool to 10 calls per minute. Rate limits are tracked per agent session and reset automatically.
Set action: deny in the PolicyLayer policy for gradle-build. The AI agent will receive a policy violation error and cannot call the tool. You can also include a reason field to explain why the tool is blocked.
gradle-build is provided by the Test MCP server (Dave-London/Pare). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.