AI agents invoke gradle-test to trigger actions in Make. 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.
The tool name strongly implies executing Gradle's test runner, which runs code on the system. The description is truncated to just 'Runs', which is uninformative but consistent with executing a command. Severity is medium as test execution can have side effects (file I/O, network calls, database changes) but is generally scoped. Confidence is slightly reduced due to the incomplete description.
From the tool's definition Tool name 'gradle-test' and description 'Runs' (truncated/uninformative) — 'gradle-test' implies executing Gradle test tasks, which runs code/build commands
Documented attack patterns abuse exactly the kind of access gradle-test gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Make, and nothing reaches the server without passing your rules. This is the rule we recommend for gradle-test:
{
"version": "1",
"default": "deny",
"tools": {
"gradle-test": {
"limits": [
{
"counter": "gradle-test_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
}gradle-test stays usable, but rate-capped — a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Runs. It is categorised as a Execute tool in the Make MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Make MCP server in PolicyLayer and add a rule for gradle-test: 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 Make. Nothing to install.
gradle-test 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-test 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-test. 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-test is provided by the Make MCP server (Dave-London/Pare). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Make, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
202 Make tools catalogued and risk-classified — across an index of 43,000+ MCP servers.