Deletes a file or directory inside the selected LocalWP site. Requires the
AI agents call delete_site_file to permanently remove resources in LocalWP MCP — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
This tool removes files or directories from a WordPress site without the ability to undo the action (unless backups exist separately). Deletion of site files can break functionality, expose security vulnerabilities, or cause data loss. While not directly financial, it ranks as Destructive due to its irreversible nature and potential for significant harm to site integrity.
From the tool's definition Tool name 'delete_site_file' and description 'Deletes a file or directory inside the selected LocalWP site' explicitly indicate irreversible deletion of data.
Attacks that exploit this kind of access
Deletes a file or directory inside the selected LocalWP site. Requires the. It is categorised as a Destructive tool in the LocalWP MCP MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the LocalWP MCP server in PolicyLayer and add a rule for delete_site_file: 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 LocalWP MCP. Nothing to install.
delete_site_file 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_file 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_file. 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_file is provided by the LocalWP MCP server (kazimshah39/localwp-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 →