List best power curves for the athlete
AI agents call listAthletePowerCurves 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 |
|---|---|---|---|
f1 | array | Yes | If set each curve is returned with these filters applied to compare curves |
f2 | array | Yes | If set each curve is returned with these filters applied to compare curves |
f3 | array | Yes | If set each curve is returned with these filters applied to compare curves |
id | string | Yes | |
ext | string | Yes | |
now | string | — | Current local date (ISO-8601) |
type | string | Yes | 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 |
curves | array | — | Comma separated list of curves to return (default last year) |
newest | string | — | |
pmType | string | — | |
filters | array | — | Only consider activities matching all the filters in this list |
includeRanks | boolean | — |
Parameters from the server's own tool schema.
The verb 'list' and the retrieval-focused description clearly indicate this tool queries existing data (power curve metrics) for an athlete without creating, modifying, deleting, or executing any operations.
From the tool's definition Tool name 'listAthletePowerCurves' and description 'List best power curves for the athlete' indicate a retrieval/query operation with no side effects.
Risk signalsAccepts freeform code/query input (filters[].code) · High parameter count (37 properties)
Attacks that exploit this kind of access
List best power curves for the athlete. It is categorised as a Read tool in the Intervals Icu Api MCP Server, which means it retrieves data without modifying state.
listAthletePowerCurves accepts 12 parameters: f1, f2, f3, id, ext, now, type, curves, newest, pmType, filters, includeRanks. Required: f1, f2, f3, id, ext, type. 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 listAthletePowerCurves: 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.
listAthletePowerCurves 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 listAthletePowerCurves 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 listAthletePowerCurves. 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.
listAthletePowerCurves 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 →