Get a list of activities for an athlete from Intervals.icu Args: athlete_id: The Intervals.icu athlete ID (optional, will use ATHLETE_ID from .env if not provided) api_key: The Intervals.icu API key (optional, will use API_KEY from .env if not provided) start_date: Start date in YYYY-MM-DD format...
AI agents call get_activities 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 retrieves fitness data (activities) from the Intervals.icu API without side effects. It queries existing data with optional filters (date range, limit, unnamed inclusion) but does not create, modify, delete, or execute any operations.
From the tool's definition Tool description states 'Get a list of activities for an athlete' with parameters for filtering by date range and limit. No modification, deletion, or execution capabilities are present.
Documented attack patterns abuse exactly the kind of access get_activities 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_activities:
{
"version": "1",
"default": "deny",
"tools": {
"get_activities": {}
}
}get_activities 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 a list of activities for an athlete from Intervals.icu Args: athlete_id: The Intervals.icu athlete ID (optional, will use ATHLETE_ID from .env if not provided) api_key: The Intervals.icu API key (optional, will use API_KEY from .env if not provided) start_date: Start date in YYYY-MM-DD format (optional, defaults to 30 days ago) end_date: End date in YYYY-MM-DD format (optional, defaults to today) limit: Maximum number of activities to return (optional, defaults to 10) include_unnamed: Whether to include unnamed activities (optional, defaults to False). 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_activities: 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_activities 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_activities 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_activities. 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_activities 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.