Governed ability
Update menu
aafm/update-menu Guarded write
Renames a navigation menu by id. Requires the edit-theme-options capability.
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 menu ships switched off. You turn it on one at a time, and an update never widens access on its own.
- Guarded write
Writes stay conservative, and the plugin re-checks the capability before the call runs.
- Capability gated
A connection only sees Update menu 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 but never the values.
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.
Rename the menu with id 3 to Primary Menu.
Change the name of the footer menu.
Update this navigation menu title.
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 menu.
What can it change?
It renames a navigation menu by id. It requires the edit-theme-options capability.
Does it touch the menu items?
No. It only changes the menu name. Items are managed with the menu item abilities.
Is it on by default?
No, and each rename is written to the audit log.
Governed by default, from the first call.
Update menu 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.