stop_tomcat · Gradle Tomcat MCP Server MCP: Risk & Policy

WHAT IT DOES

What stop_tomcat does on Gradle Tomcat MCP Server

AI agents invoke stop_tomcat to trigger actions in Gradle Tomcat 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_tomcat needs a policy

This tool executes a command that terminates the Tomcat process. While not destructive (data is not deleted/overwritten), it is an Execute action because it triggers an external operation (process termination) whose effects are immediate and consequential. Stopping a live application server disrupts service availability.

From the tool's definition Tool named 'stop_tomcat' with description 'Terminate Tomcat process' — directly invokes a process termination action on a running server.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

stop_tomcat Rate-limited

stop_tomcat 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_tomcat": {
      "limits": [
        {
          "counter": "stop_tomcat_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 Tomcat MCP Server, so you can run agents against it safely.

FAQ

Questions about stop_tomcat

What does the stop_tomcat tool do? +

Terminate Tomcat process. It is categorised as a Execute tool in the Gradle Tomcat 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_tomcat? +

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

What risk level is stop_tomcat? +

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

Can I rate-limit stop_tomcat? +

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

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

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