mcp_delete_menu_item
Delete a menu item. Its children move up to its own parent; the response lists them as reparented.
This record as markdown: /tools/io-github-cvrt-jh-wordpress-mcp/mcp-delete-menu-item.md
What mcp_delete_menu_item does on Wordpress
AI agents call mcp_delete_menu_item to permanently remove resources in Wordpress, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Why mcp_delete_menu_item is rated Critical
Permanently deletes menu items without undo capability; cascading restructuring effects qualify as destructive.
From the tool's definition Delete a menu item; children reparented; irreversible operation.
Attacks that exploit this kind of access
The rule that runs mcp_delete_menu_item safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Wordpress, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For mcp_delete_menu_item, this is the rule to start with:
mcp_delete_menu_item 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 Wordpress, apply this rule, and every mcp_delete_menu_item call is checked against it from then on.
Questions about mcp_delete_menu_item
Delete a menu item. Its children move up to its own parent; the response lists them as reparented. It is categorised as a Destructive tool in the Wordpress MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Wordpress MCP server in PolicyLayer and add a rule for mcp_delete_menu_item: 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 Wordpress. Nothing to install.
mcp_delete_menu_item 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 mcp_delete_menu_item 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 mcp_delete_menu_item. 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.
mcp_delete_menu_item is provided by the Wordpress MCP server (@cavort-it-systems/wordpress-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Wordpress, and thousands of servers like it.
Across the catalogue