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

WHAT IT DOES

What postgres-stop does on Dokploy MCP Server

AI agents invoke postgres-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 postgres-stop needs a policy

This tool executes a command to stop a running PostgreSQL service, which is an irreversible operational action with significant side effects (service downtime, connection termination, potential data consistency issues). While the action itself is theoretically reversible via restart, the immediate destructive impact on availability and ongoing operations qualifies it as Execute rather than Write.

From the tool's definition Tool name 'postgres-stop' and description 'Stops a PostgreSQL database in Dokploy' indicate execution of an operational command that triggers an external system state change (database service shutdown).

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

postgres-stop Rate-limited

postgres-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": {
    "postgres-stop": {
      "limits": [
        {
          "counter": "postgres-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 postgres-stop

What does the postgres-stop tool do? +

Stops a PostgreSQL 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 postgres-stop? +

Register the Dokploy MCP Server MCP server in PolicyLayer and add a rule for postgres-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 postgres-stop? +

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

Can I rate-limit postgres-stop? +

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

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

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