claudeus_wp_templates__delete_template
Delete a custom template. Removes user-created templates (theme templates cannot be deleted).
This record as markdown: /tools/deus-h-claudeus-wp-mcp/claudeus-wp-templates--delete-template.md
What claudeus_wp_templates__delete_template does on Claudeus WordPress MCP
AI agents call claudeus_wp_templates__delete_template 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_templates__delete_template is rated Critical
This tool performs an irreversible deletion operation on WordPress templates. Once deleted, custom templates cannot be recovered without a backup. While the blast radius is somewhat mitigated by the constraint that only user-created templates can be deleted (not theme templates), deletion operations are categorically Destructive.
From the tool's definition Tool name contains 'delete_template' and description states 'Delete a custom template. Removes user-created templates'. The verb 'delete' and 'removes' indicate irreversible data destruction.
Attacks that exploit this kind of access
The rule that runs claudeus_wp_templates__delete_template 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_templates__delete_template, this is the rule to start with:
claudeus_wp_templates__delete_template 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_templates__delete_template call is checked against it from then on.
Questions about claudeus_wp_templates__delete_template
Delete a custom template. Removes user-created templates (theme templates cannot be deleted). 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_templates__delete_template: 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_templates__delete_template 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_templates__delete_template 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_templates__delete_template. 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_templates__delete_template 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