Delete a WordPress page
AI agents call delete_page to permanently remove resources in Noleemits Vision Builder MCP — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Deleting a WordPress page is an irreversible action that permanently removes content and cannot be undone through normal means. This is a destructive operation as defined: it 'irreversibly deletes or overwrites data, or actions that cannot be undone.' While the blast radius depends on the importance of the page being deleted, the capability itself represents a high-severity risk because an AI agent could…
From the tool's definition Tool name is 'delete_page' with description 'Delete a WordPress page'. The verb 'delete' combined with page deletion is explicitly destructive and irreversible.
Attacks that exploit this kind of access
Delete a WordPress page. It is categorised as a Destructive tool in the Noleemits Vision Builder MCP MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Noleemits Vision Builder MCP server in PolicyLayer and add a rule for delete_page: 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 Noleemits Vision Builder MCP. Nothing to install.
delete_page 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_page 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_page. 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_page is provided by the Noleemits Vision Builder MCP server (noleemits/vision-builder-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 →