DELETE a site permanently — removes its nginx vhost, files, and system user. Irreversible. Double-check the site_id with get_site first.
AI agents call delete_site to permanently remove resources in Ploi MCP Server — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
The tool permanently deletes site infrastructure (nginx vhost, files, system user) with no undo capability. This is explicitly irreversible data destruction affecting production systems, matching the Destructive category definition. The critical severity reflects the blast radius: an agent error could eliminate customer sites, configurations, and hosted content without recovery.
From the tool's definition DELETE a site permanently — removes its nginx vhost, files, and system user. Irreversible.
Attacks that exploit this kind of access
DELETE a site permanently — removes its nginx vhost, files, and system user. Irreversible. Double-check the site_id with get_site first. It is categorised as a Destructive tool in the Ploi MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Ploi MCP Server 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 Ploi MCP Server. 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 Ploi MCP Server MCP server (sudanese/ploi-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 →