Governed ability
List Avada elements
aafm/avada-list-elementsRead only
List Avada elements is a governed ability in Agent Abilities for MCP, a free WordPress plugin that runs an MCP server on your site.
Lists the elements Avada Builder has on this site, from Avada's own element map: tag, name, whether it holds other elements, and the one child element a parent element such as tabs takes. With tag it returns one element with its settings, each under the name Avada stores it (a padding setting is one per side): kind, label, default, the allowed values of a choice (at most 100), whether avada-update-element can write it, and needs, which is unfiltered_html for settings that can carry script or raw HTML. Typography and dynamic data settings are listed but cannot be written. The tablet, phone and hover variants Avada's builder adds are listed as settings of their own. Requires the edit_posts capability; 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, List Avada elements ships switched off. You turn it on one at a time, and an update never switches on a tool it serves.
- Reads only
It reads data and returns it to your client. Nothing on your site is created, changed, or removed.
- Capability gated
A connection only sees List Avada elements 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.
List Avada elements 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.
List the elements Avada Builder has on this site.
Show me every setting of the Avada button element.
Which settings of the title element can be written?
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 List Avada elements.
Where does the list come from?
From Avada's own element map: each element's tag, name, whether it holds other elements, and with tag, its settings under the names Avada stores them, with their kind, default, allowed values and whether Update an Avada element can write them.
Are any settings off limits?
Typography and dynamic data settings are listed but cannot be written, and settings that can carry script or raw HTML are marked as needing unfiltered_html.
Governed by default, from the first call.
List Avada elements 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.