Governed ability
List blocks
aafm/list-blocks Read only
Lists reusable blocks (synced patterns) by id, title, slug, status, and modified date. No block markup in the list. Response includes total (the query-wide count of matching blocks). Requires the edit-posts capability.
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, List blocks 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 List blocks 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 all the reusable blocks on the site with their titles and last modified dates.
List the synced patterns and tell me which ones are published.
Which reusable blocks exist, and what are their slugs?
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 List blocks.
Does this return the block content?
No. The list gives you each reusable block's id, title, slug, status, and modified date only. To read the actual markup, use the Get block ability on a specific id.
What permission does listing blocks need?
It requires the edit-posts capability, and like every ability it stays off until an administrator turns it on and remains capability-gated once enabled.
Is a read like this logged?
Yes. Every call is written to the plugin's own audit log with the acting user and timestamp, whether it succeeds, errors, or is denied.
Governed by default, from the first call.
List blocks 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.