restart_database

Restart a database.

SERVERCoolify SOURCEcoolify-mcp-server

High RISK CLASS

Category Execute

Parameters 00 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/coolify/restart-database.md

WHAT IT DOES

What restart_database does on Coolify

AI agents invoke restart_database to trigger actions in Coolify. 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.

RISK

Why restart_database is rated High

This tool triggers a restart of a running database service, which is a side-effecting external operation that falls under Execute rather than Write (not creating/modifying data reversibly) or Destructive (restart is typically reversible and does not delete data).

From the tool's definition Tool name 'restart_database' and description 'Restart a database.' indicate execution of an external operation (database service restart) whose effects depend on which database is targeted as an argument.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs restart_database safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Coolify, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For restart_database, this is the rule to start with:

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.

The button opens the PolicyLayer dashboard: create your workspace, connect Coolify, apply this rule, and every restart_database call is checked against it from then on.

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 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 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. 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 server (coolify-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Coolify, and thousands of servers like it.

This server

All 111 Coolify tools → High-risk tools on this server →

Across the catalogue

All high-risk MCP tools → The MCP Attack Database →

Guides

Govern code and CI agents →Agent sandbox →Least privilege for MCP →