start_database · Coolify MCP Server MCP: Risk & Policy

WHAT IT DOES

What start_database does on Coolify MCP Server

AI agents invoke start_database to trigger actions in Coolify 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 start_database needs a policy

This tool executes a command that starts a database service, which is an external operation with side effects that cannot be instantly reversed (service startup state changes). It is not a simple Read (no data retrieval), not a Write (does not create/modify persistent data), not Destructive (does not delete/irreversibly alter data), and not Financial.

From the tool's definition start_database: Start a database - this triggers an external operation (database service startup) whose effects depend on which database is targeted and the current system state.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

start_database Rate-limited

start_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": {
    "start_database": {
      "limits": [
        {
          "counter": "start_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 Server, so you can run agents against it safely.

FAQ

Questions about start_database

What does the start_database tool do? +

Start a database. It is categorised as a Execute tool in the Coolify 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 start_database? +

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

What risk level is start_database? +

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

Can I rate-limit start_database? +

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

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

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