Governed ability
Remove a WPBakery element
aafm/wpbakery-remove-elementGuarded write
Remove a WPBakery element is a governed WPBakery Page Builder ability in Agent Abilities for MCP, a free WordPress plugin that runs an MCP server on your site.
Removes one element, with everything inside it, from a WPBakery page or Grid Builder template, named by its index and by the tag and fingerprint from the outline of wpbakery-get-page-content. The fingerprint covers the whole element, so one that gained content since the read is refused. Refused when the post keeps no revisions (a Grid Builder template keeps none) or the site keeps only one, for the page's last row or section, and when a row would be left with no column. Requires page_fingerprint from the last read or write and returns the new one; a changed page is refused and nothing is saved. Other indexes may move, so read the outline again before the next structural change. restore_revision_id brings the page back through restore-revision. The page's generated CSS is rebuilt. Not undoable from this plugin's change history. Requires edit access to the post; WPBakery's Role Manager settings are not applied, though its own save filter still runs. Only while WPBakery Page Builder is active.
How it is governed
The same model as every ability in the plugin, stated for this one.
- Off until you enable it
Like every ability, Remove a WPBakery element ships switched off. You turn it on one at a time, and an update never switches on a tool it serves.
- Guarded write
Writes stay conservative, and the plugin re-checks the capability before the call runs.
- Capability gated
A connection only sees Remove a WPBakery element if the user you connected can run it, and the plugin checks that capability again before it executes.
- Every call audited
The call is written to the log in your own database, denials included, with the argument keys and the identifiers it touched, never free-text content.
- It can delete
This ability removes an element and everything inside it, so it is marked destructive. It runs only when a revision can bring the element back, and it returns restore_revision_id for Restore revision. It is not in the Changes tab.
Remove a WPBakery element is one of the 12 governed WPBakery Page Builder abilities. See the full WPBakery Page Builder MCP integration.
See it in action
An illustrative run. Your real calls and data stay on your own site.
Try it with a prompt
Example requests you could paste to your agent.
Remove the outdated banner row from page 57.
Delete the empty text block at the end of page 57.
These are illustrative example prompts. The agent runs them as the user you connected, checked against that user's capabilities and written to your audit log.
Frequently asked
Short answers for Remove a WPBakery element.
Can a removed element come back?
Yes. Remove a WPBakery element is refused when the post keeps no revisions or the site keeps only one, so a successful removal returns restore_revision_id for Restore revision. It is not in the Changes tab.
When else is it refused?
For the page's last row or section, when a row would be left with no column, and when the element gained content since the read, because the fingerprint covers the whole element.
Governed by default, from the first call.
Remove a WPBakery element is off until you enable it, scoped to the user you connect, and logged like everything else. Turn on only what you need.
Every ability off until you enable it, capability-gated on every call.