delete_postgresql_connection_pool
Delete a connection pool from a PostgreSQL database instance
This record as markdown: /tools/takashito-linode-mcp-server/delete-postgresql-connection-pool.md
What delete_postgresql_connection_pool does on Linode MCP Server
AI agents call delete_postgresql_connection_pool 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_connection_pool is rated Critical
Deleting a connection pool is an irreversible action that removes database connectivity infrastructure. While not as severe as deleting the database itself, it can cause application outages and cannot be undone without manual reconfiguration. This fits the Destructive category as it removes data/configuration that cannot be automatically recovered.
From the tool's definition Tool name contains 'delete' and description states 'Delete a connection pool from a PostgreSQL database instance' - this irreversibly removes database infrastructure configuration.
Attacks that exploit this kind of access
The rule that runs delete_postgresql_connection_pool 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_connection_pool, this is the rule to start with:
delete_postgresql_connection_pool 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_connection_pool call is checked against it from then on.
Questions about delete_postgresql_connection_pool
Delete a connection pool from 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_connection_pool: 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_connection_pool 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_connection_pool 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_connection_pool. 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_connection_pool 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