Governed ability

Move an Avada element

aafm/avada-move-elementGuarded write

Move an Avada element is a governed ability in Agent Abilities for MCP, a free WordPress plugin that runs an MCP server on your site.

Moves one element, with its children, to a new place on the same Avada page, layout section, library item, form or off canvas panel: before or after another element, or as its first or last child. The element and the anchor are each named by index and fingerprint from avada-get-page-content with include_structure. The element's stored text moves byte for byte; nothing is rewritten. A move to a new parent follows Avada's nesting (a container takes rows, a row takes columns, a column takes elements or nested columns, a parent element such as tabs takes only its own child element), and a reorder under the same parent is always allowed. Refused: a move into the element itself or one of its children, an element type Avada's element map does not list, a place inside an element that shows a global library item, and a move that would leave a container with no row or a row with no column. A move to the place the element already has saves nothing and returns moved false. page_fingerprint must be the one from the last read or write; the response returns the new one with the element's new index and fingerprint. 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. 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, Move 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 Move 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.

Move 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.

agent-abilities · auditGoverned
YouMove an Avada element on this site.
RunRunning aafm/avada-move-element
GateAllowedcapability re-checked before running
Auditaafm/avada-move-element · principal: editor · args: post_id
ResultApplies the change, then writes the call to the audit log.

Try it with a prompt

Example requests you could paste to your agent.

  1. Move the FAQ section on page 41 above the contact form.
  2. Put the testimonials column first in its row on 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 Move an Avada element.

Does a move rewrite the element?

No. The element's stored text moves byte for byte. A move to a new parent follows Avada's nesting, and a move into the element itself or one of its children 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.

Back to all abilities

Governed by default, from the first call.

Move 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.