Delete a calendar event
AI agents call delete_event to permanently remove resources in Mail Cal Drive — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
The tool performs an irreversible deletion operation on calendar events. Once deleted, the event cannot be recovered through normal means. While the blast radius is somewhat limited to calendar data (not financial or system-critical operations), any deletion without recovery capability qualifies as Destructive and poses a high risk if an AI agent misuses it by deleting important meetings, deadlines, or shared events…
From the tool's definition Tool name 'delete_event' combined with description 'Delete a calendar event' explicitly indicates irreversible removal of calendar data.
Attacks that exploit this kind of access
Delete a calendar event. It is categorised as a Destructive tool in the Mail Cal Drive MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Mail Cal Drive 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 Mail Cal Drive. 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 Mail Cal Drive MCP server (rumbitopi/mail-cal-drive-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →