Governed ability
Moderate comment
aafm/moderate-comment Guarded write
Approve, unapprove, spam, or trash a comment (requires moderate_comments).
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, Moderate comment 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 Moderate comment 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.
Approve the comment with id 908.
Mark comment 908 as spam.
Move that off-topic comment to the Trash.
Unapprove the comment on post 142 that needs another look.
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 Moderate comment.
What actions can it take?
It can approve, unapprove, mark as spam, or trash a comment. Trashing is recoverable, so a trashed comment can be restored.
Who can run it?
It requires the moderate_comments capability, and the ability is off by default.
Is each action recorded?
Yes. The ability name, acting user, and status are written to the audit log.
Governed by default, from the first call.
Moderate comment 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.