Governed ability
Update term
aafm/update-term Guarded write
Update a term in a public taxonomy, with a circular-hierarchy guard on reparenting.
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 term 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 term 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 category Misc to Uncategorized Archive.
Update the description on the tag with id 42.
Reparent the Sale subcategory under the Clearance category.
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 term.
Could I accidentally create a loop in the category tree?
No. Update term has a circular-hierarchy guard, so it refuses to set a term under one of its own descendants.
What can be changed?
A term in a public taxonomy, such as its name, slug, description, or parent. The change is recorded in the audit log.
Does it need a capability?
Yes. Term writes are capability-gated, and the ability is off by default.
Governed by default, from the first call.
Update term 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.