Governed ability
Get comments
aafm/get-comments Read only
List approved comments for a post (email and IP are never returned).
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, Get comments ships switched off. You turn it on one at a time, and an update never widens access on its own.
- Reads only
It reads data and returns it to your client. Nothing on your site is created, changed, or removed.
- Capability gated
A connection only sees Get comments 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.
Show me the approved comments on post 142.
List the public comments under the article with id 55.
What approved feedback do we have on this blog post?
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 Get comments.
Does it expose commenter emails or IP addresses?
No. Get comments returns approved comments only, and email and IP are never included.
Can it see the moderation queue?
No. It lists approved comments. Pending comments use the separate get pending comments ability, which requires moderate_comments.
Is it on by default?
No. It is off until enabled, and every read is audited.
Governed by default, from the first call.
Get comments 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.