Delete a range of events (planned workouts, notes etc.) from the athlete's calendar
AI agents call deleteEvents 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 | |
newest | string | — | Local date (ISO-8601) of newest event to delete (inclusive, default is all future events) |
oldest | string | Yes | Local date (ISO-8601) of oldest event to delete |
category | array | Yes | Comma separated list of event categories to delete (e.g. WORKOUT) |
createdById | string | — | If provided only events created by this athlete (created_by_id field) are deleted |
Parameters from the server's own tool schema.
This tool permanently removes data (calendar events) that cannot be recovered through the tool itself. While not financial or system-critical, deleting an athlete's planned workouts and notes represents significant irreversible harm to their training schedule and records. An AI agent misusing this with incorrect date ranges or athlete IDs could destroy weeks of training plans.
From the tool's definition Tool name 'deleteEvents' combined with description stating it deletes 'a range of events (planned workouts, notes etc.) from the athlete's calendar' — the verb 'delete' and the fact that multiple events can be removed in a range indicates irreversible data…
Attacks that exploit this kind of access
Delete a range of events (planned workouts, notes etc.) from the 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.
deleteEvents accepts 5 parameters: id, newest, oldest, category, createdById. Required: id, oldest, category. 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 deleteEvents: 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.
deleteEvents 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 deleteEvents 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 deleteEvents. 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.
deleteEvents 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 →