stop_database · Coolify MCP Tools MCP: Risk & Policy

WHAT IT DOES

What stop_database does on Coolify MCP Tools

AI agents invoke stop_database to trigger actions in Coolify MCP Tools. 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_database needs a policy

Stopping a database is an Execute-category action because it triggers an external operation (database service termination) whose effects depend on which database is targeted. It is reversible (the database can be restarted), so it is not Destructive. However, it carries high severity due to potential service outages, data access disruption, and cascading impacts on applications relying on that database.

From the tool's definition Tool explicitly performs 'Stop a database' – a reversible but operationally significant action that interrupts a live service and can affect dependent applications.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

stop_database Rate-limited

stop_database 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_database": {
      "limits": [
        {
          "counter": "stop_database_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 Coolify MCP Tools, so you can run agents against it safely.

FAQ

Questions about stop_database

What does the stop_database tool do? +

Stop a database. It is categorised as a Execute tool in the Coolify MCP Tools 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_database? +

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

What risk level is stop_database? +

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

Can I rate-limit stop_database? +

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

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

stop_database is provided by the Coolify MCP Tools MCP server (jplansink/coolify-mcp-tools). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.