This record as markdown: /tools/ai-dataecho-mcp/delete-site.md
What delete_site does on Mcp
AI agents call delete_site to permanently remove resources in Mcp, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
| Parameter | Type | Required | Description |
|---|---|---|---|
slug | string | Yes | Site slug |
Parameters from the server's own tool schema.
Why delete_site is rated Critical
This tool irreversibly removes a deployed site, destroying all associated data and configurations. While scoped to owned sites, an AI agent misusing this could cause significant unrecoverable damage to user deployments. The explicit irreversibility warning confirms the Destructive category is most appropriate, superseding any Write classification.
From the tool's definition "Permanently delete an owned site. Irreversible — confirm with the user first." The tool description explicitly states 'Permanently delete' and 'Irreversible', which are hallmarks of destructive operations that cannot be undone.
Attacks that exploit this kind of access
The rule that runs delete_site safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Mcp, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For delete_site, this is the rule to start with:
delete_site 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 Mcp, apply this rule, and every delete_site call is checked against it from then on.
Questions about delete_site
Permanently delete an owned site. Irreversible — confirm with the user first. It is categorised as a Destructive tool in the Mcp MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
delete_site accepts 1 parameter: slug. Required: slug. The full parameter table on this page comes from the server's own tool schema.
Register the MCP server in PolicyLayer and add a rule for delete_site: 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 Mcp. Nothing to install.
delete_site 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_site 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_site. 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_site is provided by the MCP server (https://dataecho.ai/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on , and thousands of servers like it.
This server
Across the catalogue