Governed ability
Create term
aafm/create-term Guarded write
Create a term in a public taxonomy (requires manage_categories).
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, Create 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 Create 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.
Create a new blog category called Release Notes.
Add a tag named Case Study to the post_tag taxonomy.
Make a child category under News called Product Updates.
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 Create term.
Who is allowed to create terms?
The call requires the manage_categories capability, so the connected agent identity must hold it. Without that capability the request is denied and the denial is logged.
Which taxonomy can it add to?
A public taxonomy on the site. Every create is written to the audit log with the acting user and timestamp.
Is this on by default?
No. It stays off until an administrator enables it.
Governed by default, from the first call.
Create 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.