Governed ability
Delete menu
aafm/delete-menu Guarded write
Permanently deletes a navigation menu and all of its items. 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, Delete 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 Delete 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.
- It can delete
This ability can delete. Where WordPress supports it, items go to Trash and can be restored, and the last administrator can never be removed.
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.
Delete the navigation menu with id 3.
Remove the old Footer Links menu and everything in it.
Get rid of this unused menu entirely.
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 Delete menu.
Is deleting a menu recoverable?
No. It permanently deletes the navigation menu and all of its items. There is no Trash for menus, so this cannot be undone.
What is required to run it?
The edit-theme-options capability. The ability is off by default.
Is it logged?
Yes. The deletion is recorded in the audit log with the acting user and timestamp.
Governed by default, from the first call.
Delete 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.