Governed ability
Update block
aafm/update-block Guarded write
Updates a reusable block's title or markup by id. The markup is sanitized. 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, Update block 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 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.
Update reusable block 42 to change its title to Spring Sale Banner.
Replace the markup of synced pattern 108 with the revised version.
Edit the Author Bio block to fix a typo in its text.
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 block.
What can it change?
Only a reusable block's title or markup, addressed by id. The markup is sanitized on save.
Who can run it?
Whoever the agent acts as must have edit access to that block. The ability is off by default, capability-gated, and each edit is recorded in the audit log.
Governed by default, from the first call.
Update 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.