Governed ability
Update an Avada element
aafm/avada-update-elementGuarded write
Update an Avada element is a governed 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 an Avada page, layout section, library item, form or off canvas panel, named by its index and by the tag and fingerprint avada-get-page-content returned with include_structure. set_atts sets settings by the names avada-list-elements gives, each value in the input form of its kind (an image as an attachment id under image_id, which writes the id and the URL together; a padding side such as padding_top as a CSS length); remove_atts takes settings off the element so Avada uses their default; text replaces the inner content of an element with no child elements. A double quote, a square bracket, two spaces in a row or a non-breaking space in a text setting is refused, because Avada's builder drops or changes it on its next save. Only a user who may post unfiltered HTML can put square brackets, percent-encoded brackets or data-* attributes in body text. Refused: a stale index or fingerprint, an element that shows a global library item (edit the item itself), a setting driven by dynamic data, a setting the element does not have or that cannot be written (typography and dynamic data cannot), a value its kind does not accept, and any change that would add or remove an element. Code blocks and settings that can carry script, such as link_attributes and custom attributes, 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, and for a layout section a user who can manage site options; Avada's Role Manager settings are not applied. Only while Avada 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 an Avada 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 an Avada 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 an Avada element is one of the 18 governed Avada abilities. See the full Avada 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.
On page 41, change the hero button text to Book a call.
Set the top padding of the second container on page 41 to 60px.
Swap the image in the about section of page 41 for attachment 512.
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 an Avada element.
How does it find the element?
By the index, tag and fingerprint Get Avada page content returns with include_structure. A stale index or fingerprint is refused, and so is any change that would add or remove an element.
What will it refuse to write?
A setting the element does not have, typography and dynamic data settings, an element that shows a global Library item, and a double quote, square bracket, two spaces in a row or a non-breaking space in a text setting. Code blocks and settings that can carry script need a user who may post unfiltered HTML.
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 an Avada 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.