Governed ability
Update WPBakery settings
aafm/wpbakery-update-settingsGuarded write
Update WPBakery settings is a governed WPBakery Page Builder ability in Agent Abilities for MCP, a free WordPress plugin that runs an MCP server on your site.
Overwrites site-wide WPBakery Page Builder settings from wpbakery-get-settings: not_responsive_css, local_google_fonts and shortcuts (true or false), google_fonts_subsets (a list), css_loading and js_loading (hybrid, optimized or legacy), and the global custom_css, custom_js_header and custom_js_footer, which also need a user who may post unfiltered HTML. Each value goes through WPBakery's own sanitize callback for that field, and a value it would change is refused. The global custom_css is the exception: it is refused when it holds markup or a "<" followed by another character, where WPBakery cuts custom.css off, and otherwise stored exactly as sent. WPBakery points each url(../ in the global CSS at its own assets folder in the custom.css file it builds; the setting itself keeps the CSS as sent. A setting whose callback cannot be found, and the Gutenberg switch, auto save and Design Options use, are not writable. The change applies to the whole site at once; previous returns the old value of every setting that changed, null where none was stored, which is the way back. A value equal to what is stored is left alone. Writing custom_css rebuilds WPBakery's custom.css file, and the call reports an error when the file does not match afterwards. Not undoable from this plugin's change history. Requires a user who can manage site options (manage_options). Only while WPBakery Page Builder 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 WPBakery 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 WPBakery 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.
- 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 WPBakery settings is one of the 12 governed WPBakery Page Builder abilities. See the full WPBakery Page Builder 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.
Switch WPBakery's CSS loading to optimized.
Turn on local Google Fonts in WPBakery.
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 WPBakery settings.
Why is it marked destructive?
Update WPBakery settings overwrites site-wide WPBakery settings and the change applies to the whole site at once. previous returns the old value of every setting that changed, which is the way back.
Which settings are off limits?
Anything outside the fixed list, a setting whose sanitize callback cannot be found, and the Gutenberg switch, auto save and Design Options use. The global CSS and JS also need a user who may post unfiltered HTML.
Governed by default, from the first call.
Update WPBakery 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.