This record as markdown: /tools/cowork-bench/delete-event.md
What delete_event does on Cowork Bench
AI agents call delete_event to permanently remove resources in Cowork Bench, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Why delete_event is rated Critical
Deletion of calendar events is an irreversible destructive action that cannot be undone through normal means. While the blast radius is somewhat limited to calendar data (not system-wide or financial), the permanent loss of scheduling information could cause significant disruption to users' workflows and commitments. This clearly falls under the Destructive category as the primary severity factor.
From the tool's definition Tool name is 'delete_event' and description states it 'Deletes an event from the calendar'. The verb 'deletes' indicates irreversible removal of data.
Attacks that exploit this kind of access
The rule that runs delete_event safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Cowork Bench, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For delete_event, this is the rule to start with:
delete_event is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.
The button opens the PolicyLayer dashboard: create your workspace, connect Cowork Bench, apply this rule, and every delete_event call is checked against it from then on.
Questions about delete_event
Deletes an event from the calendar. It is categorised as a Destructive tool in the Cowork Bench MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Cowork Bench MCP server in PolicyLayer and add a rule for delete_event: allow, deny, rate-limit, or require approval. Point your MCP client at the PolicyLayer proxy URL and the rule is enforced on every call, before it reaches Cowork Bench. Nothing to install.
delete_event is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the delete_event rule in your PolicyLayer policy. For example, setting max: 10 and window: 60 limits the tool to 10 calls per minute. Rate limits are tracked per agent session and reset automatically.
Set action: deny in the PolicyLayer policy for delete_event. The AI agent will receive a policy violation error and cannot call the tool. You can also include a reason field to explain why the tool is blocked.
delete_event is provided by the Cowork Bench MCP server (0717376/cowork_bench). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Cowork Bench, and thousands of servers like it.
Across the catalogue