Governed ability
Remove an Avada element
aafm/avada-remove-elementGuarded write
Remove an Avada element is a governed ability in Agent Abilities for MCP, a free WordPress plugin that runs an MCP server on your site.
Removes one element, with its children, from an Avada page, layout section or library item, named by its index and fingerprint from avada-get-page-content with include_structure. Every other byte of the page stays as it was. Refused before anything is saved when no revision could bring the element back: a form or an off canvas panel (they keep no revisions), revisions switched off, or a site that keeps only 1 revision per post. Also refused: the page's last top level container, or a library item's only top level element, an element inside an element that shows a global library item, and a removal that would leave a container with no row or a row with no column. page_fingerprint must be the one from the last read or write; the response returns the new one and the number of elements removed. A save that would change other content for this user is refused, and nothing is saved. restore_revision_id brings the page back through restore-revision. 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, Remove 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 Remove 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.
- 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 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.
Remove the old promo banner from page 41.
Delete the empty column in the last row of page 41.
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 an Avada element.
Can a removed element come back?
Yes. Remove an Avada element is refused before anything is saved when no revision could bring the element back, so a successful removal returns restore_revision_id for Restore revision. It is not in the Changes tab.
When is it refused?
On a form or off canvas panel, which keep no revisions, when revisions are off or the site keeps only one per post, for the page's last top level container, and when a container or row would be left empty.
Governed by default, from the first call.
Remove 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.