Governed ability

Update Avada page options

aafm/avada-update-page-optionsGuarded write

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

Sets or removes Avada page options on one post, the settings of Avada's page options panel: layout, title bar, sidebars, slider, header, footer, off canvas, form appearance, steps and confirmation, SEO and template settings from the fixed list avada-get-page-content returns with include_page_options. set maps option ids to values and remove lists ids to drop, so Avada's default applies; give at least one. Every other stored option is kept. A choice is its stored value, a color a hex, rgba, hsla or Avada color variable, an image an attachment id, and a multi choice a list. Text may hold no straight double quote or square bracket; for a user who may not post unfiltered HTML, a text or text area value WordPress would filter is refused, never stored altered. Option groups stored as several sub-values (dimensions, typography, sortable lists, media and display conditions) are not writable, and form notification, submission and privacy settings and code fields are never reachable. An empty value or default removes the option, as Avada's own save does. The old value of every option that changed comes back in previous, null where none was stored; send it back as set to undo the change. That brings back every value as Avada reads it, but not always the same stored data: an option stored as default comes back as no stored option, which Avada treats the same, and options restored after a remove may be stored in another order. A value equal to what is stored is left alone and not listed in changed. No revision is kept, and the change is not undoable from this plugin's change history. Needs the Avada theme active and a post Avada owns, one of Avada's own types, or a page, post, portfolio item, Avada Slider slide or Elastic Slider slide that no other builder owns; a portfolio item or slide also needs its content type exposed in the Content sub-tab of the Abilities tab first. Requires edit access to the post; layout sections need a user who can manage site options. Avada's Role Manager is 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 Avada page options 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 Avada page options 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 Avada page options 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
YouUpdate Avada page options on this site.
RunRunning aafm/avada-update-page-options
GateAllowedcapability re-checked before running
Auditaafm/avada-update-page-options · 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. Turn off the page title bar on page 41.
  2. Give page 41 the right sidebar and a full width layout.

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 Avada page options.

Which options can it set?

Options from the fixed list Get Avada page content returns with include_page_options: layout, title bar, sidebars, slider, header, footer, off canvas, form appearance, SEO and template settings. Options stored as several sub-values, form notification and privacy settings, and code fields are not writable.

Can I undo it?

Not from the Changes tab, which does not record this tool. The old value of every option that changed comes back in previous; send it back as set to undo the change.

Back to all abilities

Governed by default, from the first call.

Update Avada page options 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.