// SCAN REPORT

Intervals Icu MCP Server

10 tools. 4 can modify or destroy data without limits.

2 destructive tools with no built-in limits. Policy required.

Last updated: 12 Jun 2026

4 can modify or destroy data

6 read-only

10 tools total

Community server · catalogue entry verified 12/06/2026

How to control Intervals Icu MCP Server ↓

TOOL MAP

What Intervals Icu MCP Server exposes to your agents

Read (6) Write / Execute (2) Destructive / Financial (2)

Running more than one server? Check your whole stack →

MOST DANGEROUS TOOLS

Critical Risk

The most dangerous Intervals Icu MCP Server tools

Destructive · High deleteBulkEvents This tool permanently removes training events in bulk from an athlete's account. Destructive · High deleteEvent This tool permanently removes event records from the athlete's training data. Write · Medium createBulkEvents This tool creates new events in the athlete's training log, which is a reversible data modification. Write · Medium createEvent This tool creates new training event records in the Intervals.icu system.

4 of Intervals Icu MCP Server's 10 tools can modify, destroy, or commit something on every call — and an agent calls them with no built-in limits.

POLICY

How to control Intervals Icu MCP Server

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. These are the rules we recommend:

Deny destructive operations

{
  "deleteBulkEvents": {
    "deny_if": [
      {
        "conditions": [],
        "on_deny": "Blocked by default. Requires approval."
      }
    ]
  }
}

Destructive tools should never be available to autonomous agents without human approval.

Rate limit write operations

{
  "createBulkEvents": {
    "limits": [
      {
        "counter": "createbulkevents_per_hour",
        "window": "hour",
        "max": 30,
        "scope": "grant"
      }
    ]
  }
}

Prevents bulk unintended modifications from agents caught in loops.

Cap read operations

{
  "getActivities": {
    "limits": [
      {
        "counter": "getactivities_per_minute",
        "window": "minute",
        "max": 60,
        "scope": "grant"
      }
    ]
  }
}

Controls API costs and prevents retry loops from exhausting upstream rate limits.

Create a free account and register Intervals Icu MCP Server — nothing to install.
Add these rules — paste them, or build them visually. Tune the limits to your setup.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

ENFORCE POLICY ON INTERVALS ICU →

Free to start. No card required.

FULL CATALOGUE

All 10 Intervals Icu MCP Server tools

DESTRUCTIVE 2 tools

Destructive deleteBulkEvents Delete multiple events from the athlete Destructive deleteEvent Delete an event for the current athlete by event ID.

WRITE 2 tools

Write createBulkEvents Create multiple events for the current athlete in bulk. Uses the same schema as createEvent for each event. Write createEvent Create an event for the current athlete, optionally including intervals in the Native Intervals.icu Workout Fo

READ 6 tools

Read getActivities Get a list of activities for an athlete from Intervals.icu. Read getActivityDetails Get detailed information for a specific activity from Intervals.icu. Read getAthleteDetails Get athlete details. Read getEventDetails Get detailed information for a specific event from Intervals.icu. Read getEvents Get a list of events for an athlete from Intervals.icu. Read getWellnessData Get wellness data for an athlete from Intervals.icu.

EXPLORE

Related servers

Other MCP servers with similar tools — same risk classification, starter policies for each.

FAQ

Questions about Intervals Icu MCP Server

Can an AI agent delete data through the Intervals Icu MCP Server MCP server? +

Yes. The Intervals Icu MCP Server server exposes 2 destructive tools including deleteBulkEvents, deleteEvent. These permanently remove resources with no undo. PolicyLayer blocks destructive tools by default so they never reach the upstream server.

How do I prevent bulk modifications through Intervals Icu MCP Server? +

The Intervals Icu MCP Server server has 2 write tools including createBulkEvents, createEvent. Set a rate limit in your policy -- for example, 10 calls per hour prevents an agent from making more than 10 modifications per hour. PolicyLayer enforces this at the gateway, before calls reach Intervals Icu MCP Server.

How many tools does the Intervals Icu MCP Server MCP server expose? +

10 tools across 3 categories: Destructive, Read, Write. 6 are read-only. 4 can modify, create, or delete data.

How do I enforce a policy on Intervals Icu MCP Server? +

Register the Intervals Icu MCP Server MCP server in PolicyLayer, apply the suggested rules above (adjust the limits to your use case), and point your AI client at the PolicyLayer proxy URL instead of the server directly. Your agents keep the same tools; PolicyLayer evaluates every call against policy before it executes. Nothing to install, live in minutes.

Enforce policy on every Intervals Icu MCP Server tool call.

Deterministic rules across all 10 Intervals Icu MCP Server tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

ENFORCE POLICY ON INTERVALS ICU →

Free to start. No card required.

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