Delete a synced pattern (reusable block) by ID. Requires confirmDelete=true.
AI agents call wordpress_delete_reusable_block to permanently remove resources in ItchWPMCP — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
This tool permanently deletes reusable blocks from WordPress, destroying stored content without recovery possibility. While it requires confirmDelete=true as a safeguard, deletion remains the core function and is inherently irreversible. This makes it Destructive rather than Write.
From the tool's definition Tool name and description explicitly state 'Delete a synced pattern (reusable block) by ID'. The deletion is irreversible and removes stored content from WordPress.
Attacks that exploit this kind of access
Delete a synced pattern (reusable block) by ID. Requires confirmDelete=true. It is categorised as a Destructive tool in the ItchWPMCP MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the ItchWP MCP server in PolicyLayer and add a rule for wordpress_delete_reusable_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 ItchWPMCP. Nothing to install.
wordpress_delete_reusable_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 wordpress_delete_reusable_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 wordpress_delete_reusable_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.
wordpress_delete_reusable_block is provided by the ItchWP MCP server (manofsadness/itchwpmcp). 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 →