delete_calendar_event

Delete a calendar event. Get id from get_calendar_events first.

Server CoupleHub MCP Server uczesieweba/couplehub-mcp
Category Destructive
Risk class Critical
Parameters 00 required

What delete_calendar_event does on CoupleHub MCP Server

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

Why delete_calendar_event needs a policy

Deletion is irreversible and cannot be undone. Even though the blast radius is limited to a couple's shared calendar (not system-wide), the loss of scheduling information could disrupt plans and commitments. This meets the Destructive category definition: 'irreversibly deletes or overwrites data, or actions that cannot be undone.'

From the tool's definition Tool name contains 'delete' and description states 'Delete a calendar event' — this irreversibly removes data. The instruction to 'Get id from get_calendar_events first' confirms it targets specific calendar entries.

Questions about delete_calendar_event

What does the delete_calendar_event tool do? +

Delete a calendar event. Get id from get_calendar_events first. It is categorised as a Destructive tool in the CoupleHub 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_calendar_event? +

Register the CoupleHub MCP Server MCP server in PolicyLayer and add a rule for delete_calendar_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 CoupleHub MCP Server. Nothing to install.

What risk level is delete_calendar_event? +

delete_calendar_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_calendar_event? +

Yes. Add a rate_limit block to the delete_calendar_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_calendar_event completely? +

Set action: deny in the PolicyLayer policy for delete_calendar_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_calendar_event? +

delete_calendar_event is provided by the CoupleHub MCP Server MCP server (uczesieweba/couplehub-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.