wp_remove_inner_blocks

THE RISK

Critical Risk

Why wp_remove_inner_blocks needs a policy

Removing inner blocks destroys structured content (blocks) from within a parent block. While WordPress has revision history that might allow recovery, the action itself is a deletion operation with no built-in undo in the tool call itself, making it Destructive. Misuse by an AI agent could silently wipe content sections, warranting high severity.

From the tool's definition 'Remove inner blocks from a parent block' — removal of blocks is an irreversible deletion of content within the editor

Documented attack patterns abuse exactly the kind of access wp_remove_inner_blocks gives an agent:

POLICY

How to control wp_remove_inner_blocks

PolicyLayer is an MCP gateway — it sits between your AI agents and Claudaborative Editing, and nothing reaches the server without passing your rules. This is the rule we recommend for wp_remove_inner_blocks:

policy.json

{
  "version": "1",
  "default": "deny",
  "hide": [
    "wp_remove_inner_blocks"
  ]
}

wp_remove_inner_blocks disappears from the agent's tool list entirely, and any attempt to call it is denied. The rest of the server keeps working.

Create a free account and register Claudaborative Editing — nothing to install.
Add this policy — paste it, or build it visually.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

RESTRICT THIS TOOL →

Free to start. No card required.

EXPLORE

Related tools and policies

More Claudaborative Editing tools

Destructive wp_remove_blocks Remove one or more blocks from the post Destructive wp_resolve_note Resolve (delete) a note and remove its association from the linked block. Write wp_add_note Add a note (block comment) to a specific block. Notes are editorial feedback visible in th Write wp_connect Connect to a WordPress site for collaborative editing. Not needed if the server was starte Write wp_create_post Create a new WordPress post and open it for editing Write wp_edit_block_text Make surgical find-and-replace text edits within a block. Write wp_insert_block Insert a new block at a position in the post. Supports nested blocks via innerBlocks. Write wp_insert_inner_block Insert a block as a child of an existing block (e.g., add a list-item to a list)

All 32 Claudaborative Editing tools →

Destructive tools on other servers

Android Forensics ADB MCP Server create_full_backup 0xarchive web3_revoke_key Frida Game Hacking MCP clear_scan cPanel MCP Server clear_spam_box

Go deeper

Critical-risk tools in Claudaborative Editing → Every critical-risk tool this server exposes, in one view.
All critical-risk MCP tools → Every critical-risk tool across the catalogue, and the policy pattern that contains them.
The MCP Attack Database → Documented attack patterns against MCP deployments — and the policies that stop them.
Blast radius → How much damage one compromised or confused agent can do — and how to bound it.
Tool call approval → Approval gates on individual tool calls: auto-allow, prompt, or deny.
Rate Limiting MCP Tool Calls: A Practical Guide →
MCP Security: Why Prompt Guardrails Aren't Enough →

FAQ

Questions about wp_remove_inner_blocks

What does the wp_remove_inner_blocks tool do? +

Remove inner blocks from a parent block. It is categorised as a Destructive tool in the Claudaborative Editing 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 wp_remove_inner_blocks? +

Register the Claudaborative Editing MCP server in PolicyLayer and add a rule for wp_remove_inner_blocks: 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 Claudaborative Editing. Nothing to install.

What risk level is wp_remove_inner_blocks? +

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

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

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

wp_remove_inner_blocks is provided by the Claudaborative Editing MCP server (pento/claudaborative-editing). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Claudaborative Editing tool call.

Start from Claudaborative Editing, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

CHECK YOUR STACK →