Delete an event (planned workout, notes etc.) from an athlete's calendar
AI agents call deleteEvent to permanently remove resources in Intervals Icu Api — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
| Parameter | Type | Required | Description |
|---|---|---|---|
id | string | Yes | |
others | boolean | — | If true then other events added at the same time are also deleted |
eventId | number | Yes | |
notBefore | string | — | Do not delete other events on the calendar before this local date (ISO-8601) |
Parameters from the server's own tool schema.
This tool removes data that cannot be recovered through normal means. While the blast radius is limited to a single athlete's calendar events (not system-wide), deletion is irreversible and could cause loss of important planning data. Classified as Destructive rather than Write because it performs an irreversible deletion operation, not a reversible modification.
From the tool's definition deleteEvent: Delete an event (planned workout, notes etc.) from an athlete's calendar. The verb 'Delete' and the act of removing calendar items represents an irreversible data deletion.
Attacks that exploit this kind of access
Delete an event (planned workout, notes etc.) from an athlete's calendar. It is categorised as a Destructive tool in the Intervals Icu Api MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
deleteEvent accepts 4 parameters: id, others, eventId, notBefore. Required: id, eventId. The full parameter table on this page comes from the server's own tool schema.
Register the Intervals Icu Api MCP server in PolicyLayer and add a rule for deleteEvent: 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 Api. Nothing to install.
deleteEvent 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 deleteEvent 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 deleteEvent. 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.
deleteEvent is provided by the Intervals Icu Api MCP server (intervals-icu-api-mcp-server). 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 →