scale_postgres_cluster · CloudNativePG MCP Server MCP

WHAT IT DOES

What scale_postgres_cluster does on CloudNativePG MCP Server

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

Scaling a cluster is an Execute action—it triggers infrastructure operations (provisioning/deprovisioning instances) whose effects depend on the scaling argument provided. While reversible (unlike Destructive), it modifies live system state and can cause service disruption, downtime, or performance degradation if misconfigured by an agent.

From the tool's definition Tool name 'scale_postgres_cluster' with description 'Scale a PostgreSQL cluster by changing the number of instances' indicates runtime modification of infrastructure state through changing cluster size/instance count.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

scale_postgres_cluster Rate-limited

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

FAQ

Questions about scale_postgres_cluster

What does the scale_postgres_cluster tool do? +

Scale a PostgreSQL cluster by changing the number of instances. It is categorised as a Execute tool in the CloudNativePG 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 scale_postgres_cluster? +

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

What risk level is scale_postgres_cluster? +

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

Can I rate-limit scale_postgres_cluster? +

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

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

scale_postgres_cluster is provided by the CloudNativePG MCP Server MCP server (wateim/cnpg-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.