Get best HR for a range of durations for matching activities in the date range
AI agents call listActivityHRCurves 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 | |
secs | array | — | Optional durations to return (default is all, in seconds comma separated) |
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 |
Parameters from the server's own tool schema.
This tool queries and retrieves historical heart rate data from activities within a specified date range. It performs no side effects, creates no new data, executes no external commands, and does not delete or modify existing records. The low severity reflects minimal risk from misuse—an agent retrieving HR curves cannot cause damage to the system or user data.
From the tool's definition Tool name 'listActivityHRCurves' and description 'Get best HR for a range of durations for matching activities in the date range' indicate data retrieval with no modification.
Risk signalsAccepts freeform code/query input (filters[].code) · High parameter count (13 properties)
Attacks that exploit this kind of access
Get best HR for a range of durations 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.
listActivityHRCurves accepts 7 parameters: id, ext, secs, type, newest, oldest, filters. 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 listActivityHRCurves: 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.
listActivityHRCurves 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 listActivityHRCurves 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 listActivityHRCurves. 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.
listActivityHRCurves 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 →