Governed ability
Update a WPBakery element
aafm/wpbakery-update-elementGuarded write
Update 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.
Changes the settings or the inner text of one element on a WPBakery page or Grid Builder template, named by its index and by the tag and fingerprint wpbakery-get-page-content returned with include_structure. set_atts sets settings, each value in the form wpbakery-list-elements gives as its kind (a link as url, title, target and rel; an image as an attachment id; Design Options as fields such as margin_top, never as CSS); remove_atts returns settings to their default; text replaces the inner content of an element that has a content setting and no child elements. Only a user who may post unfiltered HTML can put square brackets, percent-encoded brackets or data-* attributes in body text, and even then text that would add an element is refused. Only the element's opening tag and, for text, its inner content change; every other byte of the page stays as it was. Refused: a stale index or fingerprint, a setting the element does not have or that cannot be written, a value its kind does not accept, already encoded values, and any change that would add or remove an element. Design Options and settings that can carry script or raw HTML need a user who may post unfiltered HTML. A save that would change other content for this user is refused, and nothing is saved. When a revision is kept, restore_revision_id brings the page back through restore-revision; the response also returns the element's new fingerprint and the page fingerprint. The outline stops at 2,000 elements. 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, Update 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 Update 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.
Update 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.
Change the heading in the first row of page 57 to Spring opening hours.
Set the button link on page 57 to /book/.
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 Update a WPBakery element.
What else on the page changes?
Nothing. Only the element's opening tag and, for text, its inner content change; every other byte stays as it was. A stale index or fingerprint, or a change that would add or remove an element, is refused.
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.
Update 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.