Governed ability
Count posts
aafm/count-posts Read only
Count posts of an allowlisted post type: a total of active (non-trashed) items, plus a breakdown by status (publish, draft, pending, private, future, trash). Trash and auto-draft are shown in the breakdown but excluded from total.
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, Count posts 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 Count posts 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.
How many published posts do we have?
Give me a status breakdown of all posts.
Count the draft and pending posts for the news type.
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 Count posts.
What counts toward the total?
The total is active, non-trashed items. Trash and auto-draft appear in the breakdown but are excluded from the total.
Which post types can it count?
Only allowlisted post types. It is read only and every call is logged.
Governed by default, from the first call.
Count posts 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.