Governed ability
Insert a WPBakery element
aafm/wpbakery-insert-elementGuarded write
Insert 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.
Adds an element with its children to a WPBakery page or Grid Builder template, before or after an element from the outline of wpbakery-get-page-content or as its first or last child; element takes tag, atts in the input form of each kind from wpbakery-list-elements, text and children. WPBakery's own nesting rules apply: the top level takes rows and sections, a row takes columns, a column takes content elements or an inner row. At most 50 elements, nested at most 6 deep. On an empty post with no builder, leave out the anchor to start the page; this one check follows WPBakery's own setting for which post types its editor is on for. Raw HTML, raw JS, maps, custom onclick settings and Design Options need a user who may post unfiltered HTML, and only such a user can put square brackets, percent-encoded brackets or data-* attributes in body text. 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. When a revision is kept, 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, Insert 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 Insert 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.
Insert 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.
Add a row with two columns at the end of page 57.
Insert a text block under the gallery on 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 Insert a WPBakery element.
Can it add elements inside a flexbox or grid container?
No. WPBakery 9.1 ships its flexbox and grid containers without registering them, so elements cannot be added to them or moved into them. Elements already inside can be edited, reordered or removed.
Can I undo it?
Not from the Changes tab, which does not record this tool. When a revision is kept, restore_revision_id brings the page back through Restore revision.
Governed by default, from the first call.
Insert 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.