Governed ability
Update an Avada layout
aafm/avada-update-layoutGuarded write
Update an Avada layout is a governed ability in Agent Abilities for MCP, a free WordPress plugin that runs an MCP server on your site.
Overwrites the sections and conditions of one Avada layout, named by its id from avada-list-layouts or "global" for the Global Layout. sections assigns a published layout section of the matching type to header, page_title_bar, content or footer, or 0 to clear that slot; the other slots are kept. conditions replaces the whole stored list: each condition takes mode (include or exclude), type, and under the key named by type a condition id that Avada's Layouts screen offers, or, for one specific page, post, term or author, the id Avada stores for it, such as specific_page|42, with parent set to the part of that id before the |: {"mode": "include", "type": "singular", "singular": "specific_page|42", "parent": "specific_page"}. Give at least one of sections and conditions. Pages pick their layout from these conditions, so the change applies site-wide at once. The old sections and conditions come back in previous; send them back to undo the change. A layout is never created or deleted. A change equal to what is stored is left alone and changed is false. Not undoable from this plugin's change history. Requires a user who can manage site options (manage_options). 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 layout 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 layout 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 overwrites site-wide settings in one call, so it is marked destructive. The earlier values come back in previous, and sending them back restores them. It is not in the Changes tab.
Update an Avada layout 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.
Use the Shop header section on the layout for product pages.
Make the Landing layout apply to page 42 only.
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 layout.
Why is it marked destructive?
Pages pick their layout from these conditions, so a change applies site-wide at once, and conditions replace the whole stored list. The old sections and conditions come back in previous; send them back to undo it.
Can it create a layout?
No. A layout is never created or deleted. It needs the manage_options capability.
Governed by default, from the first call.
Update an Avada layout 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.