restart_tomcat · Gradle Tomcat MCP Server MCP: Risk & Policy

WHAT IT DOES

What restart_tomcat does on Gradle Tomcat MCP Server

AI agents invoke restart_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 restart_tomcat needs a policy

restart_tomcat executes a complex operation with external side effects: it halts a running application server and restarts it. While not destructive (data is not deleted) or financial, it is Execute-category because it runs a system-level operation whose effects depend on the current state.

From the tool's definition Tool description states 'Stop and start Tomcat' — this directly triggers external process control operations (stopping and starting a service). The sibling tools include start_tomcat and stop_tomcat, confirming this is an operational control action.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

restart_tomcat Rate-limited

restart_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": {
    "restart_tomcat": {
      "limits": [
        {
          "counter": "restart_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 restart_tomcat

What does the restart_tomcat tool do? +

Stop and start Tomcat. 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 restart_tomcat? +

Register the Gradle Tomcat MCP Server MCP server in PolicyLayer and add a rule for restart_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 restart_tomcat? +

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

Can I rate-limit restart_tomcat? +

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

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

restart_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.