Governed ability
Update comment
aafm/update-comment Guarded write
Edit a comment's content (requires edit access to that comment).
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 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 Update 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.
Fix the typo in comment 908.
Update the text of the comment with id 512.
Edit that comment to remove the broken link.
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 comment.
What can it change?
It edits a comment content. It requires edit access to that specific comment.
Does it change approval status?
No. Editing content is separate from moderation, which uses the moderate comment ability.
Is it recorded and off by default?
Yes. Each edit is audited, and the ability is off until an administrator enables it.
Governed by default, from the first call.
Update 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.