Governed ability
Update template
aafm/update-template Guarded write
Updates a database block template by id. Its markup is sanitized, and theme-file templates cannot be edited. Requires the edit-theme-options 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, Update template 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 template 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 the database copy of the single template with revised markup.
Change the footer template part to add a copyright line.
Edit the archive block template to adjust its layout.
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 template.
Can it edit any template?
No. It updates database block templates only. Theme-file templates cannot be edited through it, and the markup is sanitized on save.
What does it require?
The edit-theme-options capability. It is off by default and each edit is recorded in the audit log.
Governed by default, from the first call.
Update template 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.