Delete a DigitalOcean droplet
AI agents call do_delete_droplet to permanently remove resources in Cargoshipper — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
This tool permanently removes a DigitalOcean droplet (virtual machine instance) and cannot be undone. Droplets may contain running services, data, and configurations. Misuse by an AI agent could cause significant operational disruption and data loss. This is the most severe category applicable (Destructive > Execute > Write > Read).
From the tool's definition Tool name is 'do_delete_droplet' with description 'Delete a DigitalOcean droplet'. The verb 'delete' combined with deletion of infrastructure resources (droplets/VMs) is irreversible.
Attacks that exploit this kind of access
Delete a DigitalOcean droplet. It is categorised as a Destructive tool in the Cargoshipper MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Cargoshipper MCP server in PolicyLayer and add a rule for do_delete_droplet: 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 Cargoshipper. Nothing to install.
do_delete_droplet 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 do_delete_droplet 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 do_delete_droplet. 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.
do_delete_droplet is provided by the Cargoshipper MCP server (scarr7981/cargoshipper-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the 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 →