Summary information for followed athletes
AI agents call getAthleteSummary 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 | |
end | string | — | Local date and optional time (ISO-8601) for newest data to return, default is today |
ext | string | Yes | |
tags | array | — | Optional list of athlete tags, only athletes with one of these tags are returned |
start | string | — | Local date and optional time (ISO-8601) for oldest data to return, default is 6 days ago |
Parameters from the server's own tool schema.
This tool queries and returns summary data about athletes. It has no side effects, does not modify any state, and does not execute commands or trigger external operations. It fits squarely into the Read category. Severity is low because even if an AI agent accesses this tool, it can only retrieve existing data about followed athletes, with minimal risk to the system or user.
From the tool's definition Tool name is 'getAthleteSummary' and description states it retrieves 'Summary information for followed athletes' — a pure data retrieval operation with no modification, deletion, or execution capabilities.
Attacks that exploit this kind of access
Summary information for followed athletes. It is categorised as a Read tool in the Intervals Icu Api MCP Server, which means it retrieves data without modifying state.
getAthleteSummary accepts 5 parameters: id, end, ext, tags, start. Required: id, ext. 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 getAthleteSummary: 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.
getAthleteSummary 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 getAthleteSummary 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 getAthleteSummary. 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.
getAthleteSummary 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 →