Governed ability
Update event
aafm/tec-update-eventGuarded write
Update event is a governed The Events Calendar ability in Agent Abilities for MCP, a free WordPress plugin that runs an MCP server on your site.
Update an event by ID via the Events Calendar ORM. Requires edit access to that event. Status changes route through the same shared status-authority chokepoint as update-post; organizer_ids and all_day map onto the real ORM repository behavior (clearing with an empty array, and un-setting the all-day meta key rather than writing a falsy value).
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 event 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 event 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 event is one of the 13 governed The Events Calendar abilities. See the full The Events Calendar MCP integration.
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.
Change the start time of event 512 to 6pm.
Move event 88 to a different venue and update its description.
Replace the organizers on this event with organizer 41.
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 event.
Who can change an event?
Update event requires edit access to that specific event. Status changes route through the same status authority chokepoint that update-post uses, so publishing is a separate gate.
How do organizers and all day events behave?
organizer_ids and all_day map onto the real ORM repository behavior: passing an empty array clears the organizers, and turning off all day un-sets the meta key rather than writing a falsy value.
Is the change recorded?
Yes. Update event is off by default, capability gated, and every update is written to the audit log.
Governed by default, from the first call.
Update event 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.