List events (planned workouts, notes etc.) on the athlete's calendar, add .csv for CSV output
AI agents call listEvents to retrieve information from Intervals Icu Api without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
id | string | Yes | |
ext | string | — | Convert workouts to this format (zwo, mrc, erg or fit) and add workout_filename and workout_file_base64 to workout object |
limit | number | — | Max number of events to return (default is all events) |
format | string | Yes | |
locale | string | — | Locale (en, es, de etc.) to use for workouts with steps in multiple languages |
newest | string | — | Local date (ISO-8601) for newest event to return (inclusive), default is oldest plus 6 days |
oldest | string | — | Local date (ISO-8601) for oldest event to return, default is today in the athletes timezone |
hrRange | number | — | Percentage used to convert fixed HR targets into a range (default is 1.5 or whatever is configured in the Garmin box in /settings) |
resolve | boolean | — | Resolve power, heart rate and pace targets to watts, bpm and m/s respectively |
category | array | — | Comma separated list of categories to filter for (e.g. WORKOUT,NOTES) |
paceRange | number | — | Percentage used to convert fixed pace targets into a range (default is 2.5 or whatever is configured in the Garmin box in /settings) |
powerRange | number | — | Percentage used to convert fixed power targets into a range for outdoor workouts only (default is 2.5 or whatever is configured in the Garmin box in /settings) |
Parameters from the server's own tool schema.
This tool retrieves and lists calendar events without creating, modifying, or deleting data. It is a straightforward query operation with no side effects. The low severity reflects minimal risk even if misused by an AI agent—reading calendar data poses no destructive or financial harm.
From the tool's definition Tool name 'listEvents' and description 'List events (planned workouts, notes etc.) on the athlete's calendar' indicate data retrieval only. The mention of '.csv for CSV output' confirms read-only functionality with no modification capability.
Risk signalsHigh parameter count (13 properties)
Attacks that exploit this kind of access
List events (planned workouts, notes etc.) on the athlete's calendar, add .csv for CSV output. It is categorised as a Read tool in the Intervals Icu Api MCP Server, which means it retrieves data without modifying state.
listEvents accepts 12 parameters: id, ext, limit, format, locale, newest, oldest, hrRange, resolve, category, paceRange, powerRange. Required: id, format. 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 listEvents: 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.
listEvents is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the listEvents 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 listEvents. 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.
listEvents 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 →