Governed ability
Update page
aafm/update-pageGuarded write
Update page is a governed ability in Agent Abilities for MCP, a free WordPress plugin that runs an MCP server on your site.
Update an existing page by ID (publishing is a separate gate). Optional: slug, featured_media (attachment id), terms ({taxonomy: [termId]}, replaces existing terms per taxonomy), and meta ({key: value}, allowlisted keys only).
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 page 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 page 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 and the identifiers it touched, never free-text content.
Update page is one of the 26 governed Content abilities. Browse the other Content abilities in the catalog.
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 page 12 with this revised copy.
Change the slug of the pricing page to plans.
Set the featured image on the About page to attachment 140.
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 page.
Can it publish a draft page?
Update page treats publishing as a separate gate, so changing content is one permission and moving a page to published requires the publish capability.
Is the change reversible?
WordPress keeps revisions of the page, and the Update page ability is off by default, needs edit access, and is logged.
Governed by default, from the first call.
Update page 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.