postgres-saveExternalPort · Dokploy MCP Server MCP

WHAT IT DOES

What postgres-saveExternalPort does on Dokploy MCP Server

AI agents use postgres-saveExternalPort to create or update resources in Dokploy MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Dokploy MCP Server environment.

WHY IT NEEDS A POLICY

Why postgres-saveExternalPort needs a policy

This tool modifies PostgreSQL database configuration by updating external port settings, which is a reversible write operation. While not destructive or financial, changing port configurations could expose or alter database accessibility, creating a high-severity risk if an AI agent misconfigures ports (e.g., exposing the database publicly or blocking legitimate access).

From the tool's definition Tool name includes 'save' and description states it 'Saves external port configuration', indicating modification of database network configuration.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

postgres-saveExternalPort Rate-limited

postgres-saveExternalPort stays usable, but capped — an agent stuck in a loop can't make hundreds of changes 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-saveExternalPort": {
      "limits": [
        {
          "counter": "postgres-saveexternalport_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

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-saveExternalPort

What does the postgres-saveExternalPort tool do? +

Saves external port configuration for a PostgreSQL database in Dokploy. It is categorised as a Write tool in the Dokploy MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on postgres-saveExternalPort? +

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

postgres-saveExternalPort is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit postgres-saveExternalPort? +

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

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

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