stop_daemon · Gradle MCP Server MCP: Risk & Policy

WHAT IT DOES

What stop_daemon does on Gradle MCP Server

AI agents invoke stop_daemon to trigger actions in Gradle MCP Server. 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.

WHY IT NEEDS A POLICY

Why stop_daemon needs a policy

The tool executes a command to stop daemon processes, which is an active operation with side effects. While not destructive (daemons can be restarted), it meets Execute category criteria as it runs an external operation that affects system state.

From the tool's definition Tool performs 'Stop all Gradle daemons' - an active operation that terminates running processes rather than querying state. This is an Execute action that triggers external effects (process termination) whose consequences depend on which daemons are running.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

stop_daemon Rate-limited

stop_daemon 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": {
    "stop_daemon": {
      "limits": [
        {
          "counter": "stop_daemon_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Gradle MCP Server, so you can run agents against it safely.

FAQ

Questions about stop_daemon

What does the stop_daemon tool do? +

Stop all Gradle daemons. It is categorised as a Execute tool in the Gradle MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on stop_daemon? +

Register the Gradle MCP Server MCP server in PolicyLayer and add a rule for stop_daemon: 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 Gradle MCP Server. Nothing to install.

What risk level is stop_daemon? +

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

Can I rate-limit stop_daemon? +

Yes. Add a rate_limit block to the stop_daemon 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 stop_daemon completely? +

Set action: deny in the PolicyLayer policy for stop_daemon. 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 stop_daemon? +

stop_daemon is provided by the Gradle MCP Server MCP server (jermeyyy/gradle-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.