AI agents invoke gradle-build to trigger actions in Npm. 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 executes build processes which can run arbitrary code through build scripts and task definitions. The incomplete description ('Runs') is limited, but the tool name 'gradle-build' combined with the npm/pnpm server context strongly suggests execution of build operations.
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 build scripts and can compile code, run tests, and invoke arbitrary tasks defined in build.gradle files.
Attacks that exploit this kind of access
Runs. It is categorised as a Execute tool in the Npm MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Npm 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 Npm. 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 Npm MCP server (Dave-London/Pare). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.