This record as markdown: /tools/io-github-kivanccakmak-yaver/gradle-test.md
What gradle_test does on Yaver
AI agents invoke gradle_test to trigger actions in Yaver. 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.
| Parameter | Type | Required | Description |
|---|---|---|---|
directory | string | — |
Parameters from the server's own tool schema.
Why gradle_test is rated High
Running tests involves executing code (Gradle tasks, JVM processes, potentially instrumented tests). While tests are generally safe, arbitrary test execution can trigger side effects, consume resources, and the blast radius is high if misconfigured or if tests include setup/teardown scripts with destructive operations.
From the tool's definition 'Run Android unit tests' — the tool executes test code on the system
Risk signalsAccepts file system path (directory)
Attacks that exploit this kind of access
The rule that runs gradle_test safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Yaver, 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:
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.
The button opens the PolicyLayer dashboard: create your workspace, connect Yaver, apply this rule, and every gradle_test call is checked against it from then on.
Questions about gradle_test
Run Android unit tests. It is categorised as a Execute tool in the Yaver MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
gradle_test accepts 1 parameter: directory. The full parameter table on this page comes from the server's own tool schema.
Register the Yaver 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 Yaver. 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 Yaver MCP server (yaver-cli). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Yaver, and thousands of servers like it.
Across the catalogue