This record as markdown: /tools/rsp2k-mcp-vultr/delete-connection-pool.md
What delete_connection_pool does on Vultr MCP
AI agents call delete_connection_pool to permanently remove resources in Vultr MCP, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Why delete_connection_pool is rated Critical
The 'delete' operation is irreversible—once a connection pool is deleted, it cannot be recovered without manual recreation. This falls clearly into the Destructive category. Severity is high because deleting a connection pool could disrupt database connectivity for applications relying on it, causing service outages. The confidence is high because the intent is unambiguous from both the name and description.
From the tool's definition Tool name explicitly uses 'delete' action on a connection pool resource. The description states 'Delete a connection pool,' which is an irreversible operation that cannot be undone.
Attacks that exploit this kind of access
The rule that runs delete_connection_pool safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Vultr MCP, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For delete_connection_pool, this is the rule to start with:
delete_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 Vultr MCP, apply this rule, and every delete_connection_pool call is checked against it from then on.
Questions about delete_connection_pool
Delete a connection pool. It is categorised as a Destructive tool in the Vultr MCP MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Vultr MCP server in PolicyLayer and add a rule for delete_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 Vultr MCP. Nothing to install.
delete_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_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_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_connection_pool is provided by the Vultr MCP server (rsp2k/mcp-vultr). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Vultr, and thousands of servers like it.
Across the catalogue