delete_future_event

Delete a future event from the calendar.

Server Intervals Icu MCP Server moxus/intervals-icu-mcp-ts
Category Destructive
Risk class Critical
Parameters 00 required

What delete_future_event does on Intervals Icu MCP Server

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

Why delete_future_event needs a policy

This tool irreversibly deletes calendar events, which cannot be undone. Deletion is a destructive operation that removes data permanently. While the impact is scoped to calendar events (not system-critical), unauthorized or erroneous deletion of user calendar data represents a high-severity risk. The Destructive category takes precedence over Write because the action cannot be reversed.

From the tool's definition Tool name is 'delete_future_event' and description states 'Delete a future event from the calendar.' The use of 'Delete' indicates irreversible removal of data.

Questions about delete_future_event

What does the delete_future_event tool do? +

Delete a future event from the calendar. It is categorised as a Destructive tool in the Intervals Icu 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_future_event? +

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

What risk level is delete_future_event? +

delete_future_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_future_event? +

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

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

delete_future_event is provided by the Intervals Icu MCP Server MCP server (moxus/intervals-icu-mcp-ts). 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.