delete_postgresql_instance
Delete a PostgreSQL database instance
This record as markdown: /tools/takashito-linode-mcp-server/delete-postgresql-instance.md
What delete_postgresql_instance does on Linode MCP Server
AI agents call delete_postgresql_instance to permanently remove resources in Linode MCP Server, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Why delete_postgresql_instance is rated Critical
Deleting a database instance is irreversible and destroys all data stored within it. This action cannot be undone and represents complete data loss, making it the most severe risk category. The blast radius is critical because an agent error or prompt injection could result in permanent loss of production data, backups, and associated configurations.
From the tool's definition Tool name is 'delete_postgresql_instance' and description states 'Delete a PostgreSQL database instance' — the word 'Delete' indicates irreversible removal of a database.
Attacks that exploit this kind of access
The rule that runs delete_postgresql_instance safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Linode MCP Server, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For delete_postgresql_instance, this is the rule to start with:
delete_postgresql_instance is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.
The button opens the PolicyLayer dashboard: create your workspace, connect Linode MCP Server, apply this rule, and every delete_postgresql_instance call is checked against it from then on.
Questions about delete_postgresql_instance
Delete a PostgreSQL database instance. It is categorised as a Destructive tool in the Linode MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Linode MCP Server MCP server in PolicyLayer and add a rule for delete_postgresql_instance: 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 Linode MCP Server. Nothing to install.
delete_postgresql_instance is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the delete_postgresql_instance 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.
Set action: deny in the PolicyLayer policy for delete_postgresql_instance. 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.
delete_postgresql_instance is provided by the Linode MCP Server MCP server (takashito/linode-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Linode MCP Server, and thousands of servers like it.
Across the catalogue