delete_package
Delete hosting package and optionally remove files
This record as markdown: /tools/cbrown35-20i-mcp/delete-package.md
What delete_package does on 20i MCP Server
AI agents call delete_package to permanently remove resources in 20i MCP Server, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Why delete_package is rated Critical
This tool permanently deletes a hosting package and can optionally remove associated files, which is an irreversible action that destroys customer data and infrastructure. The blast radius is critical: an AI agent misusing this could wipe out a customer's entire hosting environment, websites, and data without recovery. This is a destructive operation that cannot be undone, making it the most severe category.
From the tool's definition Tool name is 'delete_package' with description stating 'Delete hosting package and optionally remove files'. The verb 'delete' combined with the capability to remove files indicates irreversible data destruction.
Attacks that exploit this kind of access
The rule that runs delete_package safely
PolicyLayer is an MCP gateway: it sits between your AI agents and 20i MCP Server, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For delete_package, this is the rule to start with:
delete_package 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 20i MCP Server, apply this rule, and every delete_package call is checked against it from then on.
Questions about delete_package
Delete hosting package and optionally remove files. It is categorised as a Destructive tool in the 20i MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the 20i MCP Server MCP server in PolicyLayer and add a rule for delete_package: 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 20i MCP Server. Nothing to install.
delete_package 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_package 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_package. 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_package is provided by the 20i MCP Server MCP server (cbrown35/20i-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on 20i MCP Server, and thousands of servers like it.
Across the catalogue