Governed ability
Delete event
aafm/tec-delete-eventGuarded write
Delete 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.
Trash an event by ID (goes to Trash, matching this plugin's trash-post convention, never a permanent delete). Requires delete access to that event.
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, Delete 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 Delete 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.
- It can delete
This ability can delete. Where WordPress supports it, items go to Trash and can be restored, and the last administrator can never be removed.
Delete 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.
Trash event 512, the workshop that was cancelled.
Move last year's duplicate event to the Trash.
Remove event 88 from the calendar so it stops showing on the site.
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 Delete event.
Is the event gone for good?
No. Delete event moves the event to the Trash, matching this plugin's convention everywhere else, and WordPress lets you restore it. There is no permanent delete here.
What permission does it need?
Delete access to that specific event. It is a guarded write that stays off until an administrator enables it.
Can I see who did it?
Yes. Every call is written to the audit log with the acting user, so a trashed event is traceable.
Governed by default, from the first call.
Delete 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.