get_intervals_session
AI agents call get_intervals_session to retrieve information from Claude Garmin without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The 'get_' prefix, combined with the server's stated purpose of 'enabling training analysis' through querying 'real metrics,' and alignment with all sibling tools which are clearly read operations, indicates this retrieves interval session data from Garmin Connect. There is no indication this tool modifies, deletes, executes commands, or moves money.
From the tool's definition Tool name 'get_intervals_session' follows the naming pattern of sibling tools (get_activities, get_activity_zones, get_bike_session, etc.), all of which are read-only getters retrieving Garmin Connect data.
Attacks that exploit this kind of access
get_intervals_session. It is categorised as a Read tool in the Claude Garmin MCP Server, which means it retrieves data without modifying state.
Register the Claude Garmin MCP server in PolicyLayer and add a rule for get_intervals_session: 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 Claude Garmin. Nothing to install.
get_intervals_session 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_intervals_session 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_intervals_session. 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_intervals_session is provided by the Claude Garmin MCP server (jack-abyss/claude-garmin). 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 →