claudeus_wp_widgets__delete_widget
Delete a widget. Remove widget instance from its sidebar permanently.
This record as markdown: /tools/deus-h-claudeus-wp-mcp/claudeus-wp-widgets--delete-widget.md
What claudeus_wp_widgets__delete_widget does on Claudeus WordPress MCP
AI agents call claudeus_wp_widgets__delete_widget 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_widgets__delete_widget is rated Critical
This tool permanently deletes widget instances from a WordPress site, which cannot be undone without manual restoration. Destructive operations have higher severity than Write operations because they cause irreversible loss of configured content. High severity reflects that an agent could remove critical site functionality (e.g., custom widgets, forms, dynamic content areas) that took effort to configure.
From the tool's definition 'Delete a widget. Remove widget instance from its sidebar permanently.' — the word 'Delete' combined with 'permanently' and 'Remove' indicates irreversible removal of data.
Attacks that exploit this kind of access
The rule that runs claudeus_wp_widgets__delete_widget 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_widgets__delete_widget, this is the rule to start with:
claudeus_wp_widgets__delete_widget 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_widgets__delete_widget call is checked against it from then on.
Questions about claudeus_wp_widgets__delete_widget
Delete a widget. Remove widget instance from its sidebar permanently. 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_widgets__delete_widget: 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_widgets__delete_widget 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_widgets__delete_widget 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_widgets__delete_widget. 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_widgets__delete_widget 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