claudeus_wp_content__delete_block
Delete a reusable block
This record as markdown: /tools/deus-h-claudeus-wp-mcp/claudeus-wp-content--delete-block.md
What claudeus_wp_content__delete_block does on Claudeus WordPress MCP
AI agents call claudeus_wp_content__delete_block to permanently remove resources in Claudeus WordPress MCP, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Why claudeus_wp_content__delete_block is rated Critical
Deletion of blocks is a destructive action that cannot be undone through normal means. While not as critical as deleting an entire site, removing reusable blocks can break layouts and pages that depend on them, affecting site functionality and content. The blast radius is significant if an AI agent mistakenly deletes blocks it should not have.
From the tool's definition The tool name explicitly contains 'delete_block' and the description states 'Delete a reusable block'. This is an irreversible deletion operation on WordPress content.
Attacks that exploit this kind of access
The rule that runs claudeus_wp_content__delete_block safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Claudeus WordPress MCP, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For claudeus_wp_content__delete_block, this is the rule to start with:
claudeus_wp_content__delete_block 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 Claudeus WordPress MCP, apply this rule, and every claudeus_wp_content__delete_block call is checked against it from then on.
Questions about claudeus_wp_content__delete_block
Delete a reusable block. It is categorised as a Destructive tool in the Claudeus WordPress MCP MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Claudeus WordPress MCP server in PolicyLayer and add a rule for claudeus_wp_content__delete_block: 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 Claudeus WordPress MCP. Nothing to install.
claudeus_wp_content__delete_block 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 claudeus_wp_content__delete_block 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 claudeus_wp_content__delete_block. 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.
claudeus_wp_content__delete_block is provided by the Claudeus WordPress MCP server (deus-h/claudeus-wp-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Claudeus WordPress, and thousands of servers like it.
Across the catalogue