Governed ability
Update venue
aafm/tec-update-venueGuarded write
Update venue 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 a venue by ID via the Events Calendar ORM. Requires edit access to that venue. Setting status to publish requires the publish_tribe_venues 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 venue 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 venue 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 venue 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.
Correct the street address on venue 41.
Rename venue 12 and update its phone number.
Publish the draft venue we created last week.
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 venue.
Who can update a venue?
Anyone with edit access to that specific venue. Setting the status to publish additionally requires the publish_tribe_venues capability.
Is the change traceable?
Yes. Update venue is off until an administrator enables it, capability gated, and every write is captured in the audit log.
Governed by default, from the first call.
Update venue 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.