wordpress_delete_widget

Delete a WordPress widget instance. Requires confirmDelete=true. Use force=true to permanently delete instead of orphaning.

Server ItchWPMCP manofsadness/itchwpmcp
Category Destructive
Risk class Critical
Parameters 00 required

What wordpress_delete_widget does on ItchWPMCP

AI agents call wordpress_delete_widget 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.

Why wordpress_delete_widget needs a policy

This tool irreversibly removes widget instances from a WordPress site. Even though it requires confirmation (confirmDelete=true), deletion cannot be undone and represents data loss. The force parameter enables permanent deletion. This fits the Destructive category (deletes data that cannot be recovered).

From the tool's definition Tool name contains 'delete'; description states 'Delete a WordPress widget instance' and 'permanently delete instead of orphaning' with force=true parameter. These are irreversible operations on WordPress content.

Questions about wordpress_delete_widget

What does the wordpress_delete_widget tool do? +

Delete a WordPress widget instance. Requires confirmDelete=true. Use force=true to permanently delete instead of orphaning. 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.

How do I enforce a policy on wordpress_delete_widget? +

Register the ItchWP MCP server in PolicyLayer and add a rule for wordpress_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 ItchWPMCP. Nothing to install.

What risk level is wordpress_delete_widget? +

wordpress_delete_widget is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.

Can I rate-limit wordpress_delete_widget? +

Yes. Add a rate_limit block to the wordpress_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.

How do I block wordpress_delete_widget completely? +

Set action: deny in the PolicyLayer policy for wordpress_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.

What MCP server provides wordpress_delete_widget? +

wordpress_delete_widget 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.

// LOOK UP ANOTHER 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 →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.