Get interval data for a specific activity from Intervals.icu This endpoint returns detailed metrics for each interval in an activity, including power, heart rate, cadence, speed, and environmental data. It also includes grouped intervals if applicable. Args: activity_id: The Intervals.icu activit...
AI agents call get_activity_intervals to retrieve information from Intervals Icu MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries and returns fitness data from Intervals.icu without modifying, deleting, or executing any operations. It is a pure read operation with minimal security impact—the worst case is unauthorized access to personal fitness metrics, which is less severe than write, destructive, or financial operations.
From the tool's definition Tool retrieves detailed metrics for intervals in an activity (power, heart rate, cadence, speed, environmental data). The description uses 'returns' and 'get' indicating data retrieval with no modifications, deletions, or side effects.
Documented attack patterns abuse exactly the kind of access get_activity_intervals gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Intervals Icu MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for get_activity_intervals:
{
"version": "1",
"default": "deny",
"tools": {
"get_activity_intervals": {}
}
}get_activity_intervals is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Get interval data for a specific activity from Intervals.icu This endpoint returns detailed metrics for each interval in an activity, including power, heart rate, cadence, speed, and environmental data. It also includes grouped intervals if applicable. Args: activity_id: The Intervals.icu activity ID api_key: The Intervals.icu API key (optional, will use API_KEY from .env if not provided). It is categorised as a Read tool in the Intervals Icu MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Intervals Icu MCP Server MCP server in PolicyLayer and add a rule for get_activity_intervals: 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 MCP Server. Nothing to install.
get_activity_intervals 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 get_activity_intervals 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 get_activity_intervals. 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.
get_activity_intervals is provided by the Intervals Icu MCP Server MCP server (mvilanova/intervals-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Intervals Icu MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
21 Intervals Icu MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.