Get custom items (charts, custom fields, zones, etc.) 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)
AI agents call get_custom_items 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 custom items (charts, custom fields, zones) for an athlete—a pure data retrieval operation with no side effects. It matches the 'Read' category definition: 'retrieves or queries data; no side effects.' The severity is low because unauthorized access would only expose personal fitness data without enabling further harmful actions on the system.
From the tool's definition Tool name is 'get_custom_items' and description states 'Get custom items'; the verb 'get' and the retrieval-only nature (no modification, creation, or deletion mentioned) indicate a read-only query operation.
Documented attack patterns abuse exactly the kind of access get_custom_items 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_custom_items:
{
"version": "1",
"default": "deny",
"tools": {
"get_custom_items": {}
}
}get_custom_items 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 custom items (charts, custom fields, zones, etc.) 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). 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_custom_items: 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_custom_items 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_custom_items 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_custom_items. 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_custom_items 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.