elementor_delete_section

Delete an Elementor section or container at a specific index. Requires confirmDelete=true. Use elementor_get_page_structure first to find the target index.

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

What elementor_delete_section does on ItchWPMCP

AI agents call elementor_delete_section 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 elementor_delete_section needs a policy

This tool irreversibly deletes page structure elements (sections/containers) from WordPress/Elementor pages. Deletion cannot be undone programmatically through this interface alone and represents permanent loss of content layout. While the confirmation flag mitigates accidental use, an AI agent with misuse intent could still destroy website structure.

From the tool's definition Tool name explicitly contains 'delete'. Description states 'Delete an Elementor section or container at a specific index' and requires 'confirmDelete=true', indicating irreversible removal of page content.

Questions about elementor_delete_section

What does the elementor_delete_section tool do? +

Delete an Elementor section or container at a specific index. Requires confirmDelete=true. Use elementor_get_page_structure first to find the target index. 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 elementor_delete_section? +

Register the ItchWP MCP server in PolicyLayer and add a rule for elementor_delete_section: 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 elementor_delete_section? +

elementor_delete_section 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 elementor_delete_section? +

Yes. Add a rate_limit block to the elementor_delete_section 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 elementor_delete_section completely? +

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

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