mysql-stop · Dokploy MCP Server MCP: Risk & Policy

WHAT IT DOES

What mysql-stop does on Dokploy MCP Server

AI agents invoke mysql-stop to trigger actions in Dokploy 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 mysql-stop needs a policy

Stopping a database is an Execute action because it triggers an external operation (service termination) whose effects are real and immediate—the database becomes unavailable. While not permanently destructive (it can be restarted), the blast radius is high: stopping a production MySQL database causes service outages and impacts dependent applications.

From the tool's definition Tool name 'mysql-stop' and description 'Stops a MySQL database in Dokploy' indicates execution of a command that terminates a running database service. This is an external operation with side effects.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

mysql-stop Rate-limited

mysql-stop 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": {
    "mysql-stop": {
      "limits": [
        {
          "counter": "mysql-stop_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 Dokploy MCP Server, so you can run agents against it safely.

FAQ

Questions about mysql-stop

What does the mysql-stop tool do? +

Stops a MySQL database in Dokploy. It is categorised as a Execute tool in the Dokploy 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 mysql-stop? +

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

What risk level is mysql-stop? +

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

Can I rate-limit mysql-stop? +

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

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

mysql-stop is provided by the Dokploy MCP Server MCP server (limehawk/dokploy-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.