Governed ability
Update Avada Slider settings
aafm/avada-update-slider-settingsGuarded write
Update Avada Slider settings is a governed ability in Agent Abilities for MCP, a free WordPress plugin that runs an MCP server on your site.
Changes the settings of one Avada Slider, the slider as a whole and not its slides, for every page that shows it. A slider is a term of Avada's slide-page taxonomy, named by term_id. set maps setting keys to values: slider_width, slider_height, nav_box_width, nav_box_height and nav_arrow_size as a number with px, %, em, rem, vh or vw; full_screen, parallax, nav_arrows, autoplay and loop as true or false; animation as fade or slide; slideshow_speed and animation_speed as whole milliseconds; typo_sensitivity and typo_factor as numbers; slider_indicator as an empty string (none), scroll_down_indicator or pagination_circles; slider_indicator_color as a color or an empty string. Values are stored as Avada's slider screen stores them, written through Avada's own slider settings code and read back. A value equal to what is stored is left alone and not listed in changed. The old value of every setting that changed comes back in previous, null where none was stored; send it back as set to undo the change. When a slider still holds settings from an old Avada version, Avada itself copies them into its current store on the first read. Not undoable from this plugin's change history. Requires a user who can manage site options (manage_options). Only while Avada is active, and the slider needs Avada Core 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 Slider settings 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 Slider settings 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 Slider settings 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.
Turn on autoplay and loop for the homepage Avada Slider.
Set the homepage slider height to 600px.
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 Slider settings.
Does it change the slides?
No. Update Avada Slider settings changes the slider as a whole, for every page that shows it. A slider is a term of Avada's slide-page taxonomy, named by term_id.
What does it need?
The manage_options capability and Avada Core active. The old values come back in previous, which you send back to undo the change.
Governed by default, from the first call.
Update Avada Slider settings 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.