Governed ability
Get block
aafm/get-block Read only
Reads one reusable block by id, including its raw block markup. Requires edit access to that block.
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 block 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 block 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 full markup of reusable block 42.
Fetch the contents of the synced pattern with id 108 so I can review it.
Pull the raw block markup for reusable block 17.
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 block.
Can this edit the block?
No, it is read only. It returns one reusable block's markup by id and never changes it. Use Update block to make edits.
What access is required?
The agent must have edit access to that specific block, the same access a logged-in editor would need. The ability is off by default and audited on every call.
Governed by default, from the first call.
Get block 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.