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

WHAT IT DOES

What postgres-start does on Dokploy MCP Server

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

This tool executes a command to start a PostgreSQL service, which is an external operation with state-changing side effects. While reversible (the database can be stopped), it triggers infrastructure changes and potential cascade effects on applications depending on the database.

From the tool's definition Tool name 'postgres-start' and description 'Starts a PostgreSQL database in Dokploy' indicates triggering of a database service whose operational effects depend on system state and context.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

postgres-start Rate-limited

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

What does the postgres-start tool do? +

Starts 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-start? +

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

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

Can I rate-limit postgres-start? +

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

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

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