Critical Risk →

deleteEvent

Delete an event for the current athlete by event ID.

How to control deleteEvent ↓

What deleteEvent does on Intervals Icu MCP Server

AI agents call deleteEvent 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.

Critical Risk

Why deleteEvent needs a policy

This tool permanently removes event records from the athlete's training data. Deletion is irreversible and cannot be undone through normal operations. While the blast radius is limited to a single event (rather than bulk deletion via deleteBulkEvents), it still qualifies as Destructive rather than Write because the operation cannot be reversed.

From the tool's definition Tool name is 'deleteEvent' and description states 'Delete an event' – the verb 'delete' indicates irreversible removal of data.

Documented attack patterns abuse exactly the kind of access deleteEvent gives an agent:

How to control deleteEvent

PolicyLayer is an MCP gateway — it sits between your AI agents and Intervals Icu MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for deleteEvent:

policy.json
{
  "version": "1",
  "default": "deny",
  "hide": [
    "deleteEvent"
  ]
}

deleteEvent disappears from the agent's tool list entirely, and any attempt to call it is denied. The rest of the server keeps working.

  1. Create a free account and register Intervals Icu MCP Server — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
RESTRICT THIS TOOL →

Free to start. No card required.

Related tools and policies

Go deeper

Questions about deleteEvent

What does the deleteEvent tool do? +

Delete an event for the current athlete by event ID. 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 deleteEvent? +

Register the Intervals Icu MCP Server 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 MCP Server. Nothing to install.

What risk level is deleteEvent? +

deleteEvent 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 deleteEvent? +

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.

How do I block deleteEvent completely? +

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.

What MCP server provides deleteEvent? +

deleteEvent is provided by the Intervals Icu MCP Server MCP server (mrgeorgegray/intervals-icu-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Intervals Icu MCP Server tool call.

Start from Intervals Icu MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

Free to start. No card required.

10 Intervals Icu MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.