New Your team’s decisions, in one playbook every coding agent works from. Never answer your agent twice

delete_event

Deletes an event.

SERVERCalendar SOURCEdeciduus/calendar-mcp
Critical RISK CLASS
Category Destructive
Parameters 00 required
Recommended Hiddensee the rule below
Registry record Grade D, identity unverified Pull the record →

This record as markdown: /tools/deciduus-calendar-mcp/delete-event.md

What delete_event does on Calendar

AI agents call delete_event to permanently remove resources in Calendar, 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

The tool permanently removes calendar events without possibility of recovery through normal means. While not as critical as financial or system-level data deletion, calendar events represent user commitments and plans. Accidental or malicious deletion could cause significant disruption to business operations, meetings, and personal schedules. The destructive nature places it above Write or Execute categories.

From the tool's definition Tool name 'delete_event' with description 'Deletes an event.' directly indicates irreversible removal of calendar data.

Questions about delete_event

What does the delete_event tool do? +

Deletes an event. It is categorised as a Destructive tool in the Calendar 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 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. 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 (deciduus/calendar-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

More on Calendar, and thousands of servers like it.

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of Calendar's. Pull the full record:

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.