// MCP TOOL REFERENCE

delete_events_by_date_range

ServerIntervals Icu MCP Server
CategoryDestructive

How to control delete_events_by_date_range ↓

WHAT IT DOES

What delete_events_by_date_range does on Intervals Icu MCP Server

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

THE RISK

Critical Risk

Why delete_events_by_date_range needs a policy

This tool performs irreversible deletion of fitness event data. Multiple events can be deleted at once via the date range parameters, creating a significant blast radius. An AI agent could accidentally or maliciously delete substantial portions of an athlete's training history.

From the tool's definition Tool name contains "delete" and description explicitly states "Delete events for an athlete from Intervals.icu in the specified date range." The tool irreversibly removes training/fitness event data within a date range.

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

POLICY

How to control delete_events_by_date_range

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 delete_events_by_date_range:

policy.json

{
  "version": "1",
  "default": "deny",
  "hide": [
    "delete_events_by_date_range"
  ]
}

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

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

RESTRICT THIS TOOL →

Free to start. No card required.

EXPLORE

Related tools and policies

More Intervals Icu MCP Server tools

Destructive delete_custom_item Delete a custom item for an athlete from Intervals.icu Args: item_id: The cus Destructive delete_event Delete event for an athlete from Intervals.icu Args: athlete_id: The Intervals Execute register_tools Register all MCP tools with the FastMCP server instance. This function imports all to Write add_activity_message Add a message (note/comment) to an activity on Intervals.icu Args: activity_i Write add_or_update_event add_or_update_event Write add_or_update_note Add or update a plain text note (category NOTE) on the Intervals.icu calendar. Args: Write create_custom_item create_custom_item Write update_custom_item update_custom_item

All 21 Intervals Icu MCP Server tools →

Destructive tools on other servers

Android Forensics ADB MCP Server create_full_backup 0xarchive web3_revoke_key Frida Game Hacking MCP clear_scan cPanel MCP Server clear_spam_box

Go deeper

Critical-risk tools in Intervals Icu MCP Server → Every critical-risk tool this server exposes, in one view.
All critical-risk MCP tools → Every critical-risk tool across the catalogue, and the policy pattern that contains them.
The MCP Attack Database → Documented attack patterns against MCP deployments — and the policies that stop them.
Blast radius → How much damage one compromised or confused agent can do — and how to bound it.
Tool call approval → Approval gates on individual tool calls: auto-allow, prompt, or deny.
Rate Limiting MCP Tool Calls: A Practical Guide →
MCP Security: Why Prompt Guardrails Aren't Enough →

FAQ

Questions about delete_events_by_date_range

What does the delete_events_by_date_range tool do? +

Delete events for an athlete from Intervals.icu in the specified date range. Args: athlete_id: The Intervals.icu athlete ID (optional, will use ATHLETE_ID from .env if not provided) api_key: The Intervals.icu API key (optional, will use API_KEY from .env if not provided) start_date: Start date in YYYY-MM-DD format end_date: End date in YYYY-MM-DD format. 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_events_by_date_range? +

Register the Intervals Icu MCP Server MCP server in PolicyLayer and add a rule for delete_events_by_date_range: 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_events_by_date_range? +

delete_events_by_date_range 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_events_by_date_range? +

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

Set action: deny in the PolicyLayer policy for delete_events_by_date_range. 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_events_by_date_range? +

delete_events_by_date_range is provided by the Intervals Icu MCP Server MCP server (mvilanova/intervals-mcp-server). 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.

CHECK YOUR STACK →

Free to start. No card required.

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