restart_database · Coolify MCP Tools MCP: Risk & Policy

WHAT IT DOES

What restart_database does on Coolify MCP Tools

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

This tool executes an operation on infrastructure (database restart) whose real-world effects depend on which database is targeted. While not destructive (data is not deleted) and not financial, it is Execute-category because it triggers external operations. Severity is high due to potential business impact: database restarts can cause downtime, interrupt active connections, and affect dependent applications.

From the tool's definition Tool name is 'restart_database' with description 'Restart a database'. Restarting a database is an operational action that triggers external system behavior with side effects that persist (service interruption, potential data consistency issues, dependent…

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

restart_database Rate-limited

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

What does the restart_database tool do? +

Restart 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 restart_database? +

Register the Coolify MCP Tools MCP server in PolicyLayer and add a rule for restart_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 restart_database? +

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

Can I rate-limit restart_database? +

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

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

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