gradle-test

Runs

SERVERNpm SOURCEDave-London/Pare

High RISK CLASS

Category Execute

Parameters 00 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/io-github-dave-london-npm/gradle-test.md

WHAT IT DOES

What gradle-test does on Npm

AI agents invoke gradle-test 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.

RISK

Why gradle-test is rated High

The tool executes Gradle test tasks, which runs arbitrary build/test code on the system. This falls under Execute as it triggers external operations (compiling and running test suites). The blast radius is high because test execution can run arbitrary code, consume significant resources, or have side effects depending on the test suite.

From the tool's definition Tool name 'gradle-test' and server description mentions running operations; 'Runs' is the start of the (truncated) description, indicating execution of Gradle test tasks

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs gradle-test safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Npm, 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 Rate-limited

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.

View as policy code

policy.json

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

RATE-LIMIT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Npm, apply this rule, and every gradle-test call is checked against it from then on.

FAQ

Questions about gradle-test

What does the gradle-test tool do? +

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.

How do I enforce a policy on gradle-test? +

Register the Npm 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 Npm. Nothing to install.

What risk level is gradle-test? +

gradle-test is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit gradle-test? +

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.

How do I block gradle-test completely? +

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.

What MCP server provides gradle-test? +

gradle-test 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.

KEEP EXPLORING

More on Npm, and thousands of servers like it.

This server

All 202 Npm tools → High-risk tools on this server →

Across the catalogue

execute_test_case on Percepta MCP Server → All high-risk MCP tools → The MCP Attack Database →

Guides

Govern code and CI agents →Agent sandbox →Least privilege for MCP →