delete_postgres_cluster

Delete a PostgreSQL cluster.

Server CloudNativePG MCP Server wateim/cnpg-mcp
Category Destructive
Risk class Critical
Parameters 00 required

What delete_postgres_cluster does on CloudNativePG MCP Server

AI agents call delete_postgres_cluster to permanently remove resources in CloudNativePG MCP Server — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.

Why delete_postgres_cluster needs a policy

Deletion of a database cluster is a destructive, irreversible operation with maximum blast radius. It exceeds Execute severity because the action cannot be undone and results in complete data loss. This is classified as Destructive per the highest-severity rule, warranting critical severity due to the potential loss of all data in the cluster and operational disruption.

From the tool's definition Tool name is 'delete_postgres_cluster' and description states 'Delete a PostgreSQL cluster.' This operation irreversibly removes an entire PostgreSQL cluster, destroying all associated data and infrastructure.

Questions about delete_postgres_cluster

What does the delete_postgres_cluster tool do? +

Delete a PostgreSQL cluster. It is categorised as a Destructive tool in the CloudNativePG MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.

How do I enforce a policy on delete_postgres_cluster? +

Register the CloudNativePG MCP Server MCP server in PolicyLayer and add a rule for delete_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 delete_postgres_cluster? +

delete_postgres_cluster is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.

Can I rate-limit delete_postgres_cluster? +

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

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

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

// LOOK UP ANOTHER SERVER

Every MCP server has a record like this.

Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.