Get the gear catalog (bikes, shoes, etc.) for an athlete from Intervals.icu. Returns one line per gear item with id, type, name, and basic stats. The result is cached for the MCP process lifetime; pass refresh=True to re-fetch. Args: athlete_id: The Intervals.icu athlete ID (optional, will use AT...
AI agents call get_gear_list 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 equipment data (bikes, shoes) from the Intervals.icu API with no side effects. It performs a simple data retrieval operation analogous to a GET request, with optional cache refresh but no create, update, or delete operations. The blast radius of misuse is minimal—an attacker gains only visibility into an athlete's gear inventory with no ability to modify or delete records.
From the tool's definition Tool retrieves a gear catalog listing with 'id, type, name, and basic stats' with no mutation or deletion capability. The description explicitly states it 'Get[s]' data and uses a read-only cache mechanism.
Documented attack patterns abuse exactly the kind of access get_gear_list 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_gear_list:
{
"version": "1",
"default": "deny",
"tools": {
"get_gear_list": {}
}
}get_gear_list 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 the gear catalog (bikes, shoes, etc.) for an athlete from Intervals.icu. Returns one line per gear item with id, type, name, and basic stats. The result is cached for the MCP process lifetime; pass refresh=True to re-fetch. 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) refresh: If True, bypass the cache and re-fetch from the API (default 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_gear_list: 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_gear_list 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_gear_list 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_gear_list. 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_gear_list 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.