Get best pace for a range of distances for matching activities in the date range
AI agents call listActivityPaceCurves 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 | Yes | |
gap | boolean | — | Return gradient adjusted pace curves |
type | string | — | The sport (Ride, Run etc.). If filters is not provided or is blank or does not contain a type filter then activities for the types of the sport matching this pa |
newest | string | Yes | Local ISO-8601 date or date and time (inclusive) |
oldest | string | Yes | Local ISO-8601 date or date and time e.g. 2019-07-22T16:18:49 or 2019-07-22 |
filters | array | — | Only return activities matching all the filters in this list |
distances | array | — | Distances required (in meters, comma separated) |
Parameters from the server's own tool schema.
The tool retrieves and queries historical activity pace data within a specified date range. The verb 'Get' and the pattern of listing/retrieving metrics (pace curves) without any modification, creation, deletion, or execution of external operations classifies this as a Read operation. The severity is low because it only exposes aggregate fitness analytics with no destructive or system-altering capability.
From the tool's definition Tool name 'listActivityPaceCurves' and description 'Get best pace for a range of distances for matching activities in the date range' indicate a retrieval/query operation with no side effects.
Risk signalsAccepts freeform code/query input (filters[].code) · High parameter count (14 properties)
Attacks that exploit this kind of access
Get best pace for a range of distances for matching activities in the date range. It is categorised as a Read tool in the Intervals Icu Api MCP Server, which means it retrieves data without modifying state.
listActivityPaceCurves accepts 8 parameters: id, ext, gap, type, newest, oldest, filters, distances. Required: id, ext, newest, oldest. 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 listActivityPaceCurves: 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.
listActivityPaceCurves 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 listActivityPaceCurves 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 listActivityPaceCurves. 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.
listActivityPaceCurves 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 →