delete_event

Delete a calendar event. For recurring events, can delete single instance, this and future, or entire series.

Server Calendar MCP Server rauf543/calendar-mcp
Category Destructive
Risk class Critical
Parameters 00 required

What delete_event does on Calendar MCP Server

AI agents call delete_event to permanently remove resources in Calendar MCP Server — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.

Why delete_event needs a policy

This tool permanently removes calendar events, which cannot be undone. Deletion is irreversible data destruction. The ability to delete entire recurring series amplifies the blast radius. While not as severe as financial or system-critical data deletion, unauthorized event deletion could disrupt business operations and meetings.

From the tool's definition Tool name is 'delete_event' and description states 'Delete a calendar event' with options to delete 'single instance, this and future, or entire series.' The word 'Delete' indicates irreversible removal of data.

Risk signalsBulk/mass operation — affects multiple targets

Questions about delete_event

What does the delete_event tool do? +

Delete a calendar event. For recurring events, can delete single instance, this and future, or entire series. It is categorised as a Destructive tool in the Calendar MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.

How do I enforce a policy on delete_event? +

Register the Calendar MCP Server 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 Calendar MCP Server. Nothing to install.

What risk level is delete_event? +

delete_event is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.

Can I rate-limit delete_event? +

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.

How do I block delete_event completely? +

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.

What MCP server provides delete_event? +

delete_event is provided by the Calendar MCP Server MCP server (rauf543/calendar-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

// LOOK UP ANOTHER 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 →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.