get_bike_session
AI agents call get_bike_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.
This tool retrieves bike session data from Garmin Connect for analysis purposes. It has no side effects—it only queries and returns existing data. Following the established pattern of all sibling tools on this server, which are uniformly read operations, this is classified as Read with low severity. An AI agent misusing this tool can only over-query or expose personal fitness data, not modify or delete it.
From the tool's definition Tool name 'get_bike_session' follows the naming pattern of sibling tools (get_activities, get_fitness, get_full_snapshot, etc.), all of which are read-only data retrieval operations. The 'get_' prefix consistently indicates query/fetch operations.
Attacks that exploit this kind of access
get_bike_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_bike_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_bike_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_bike_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_bike_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_bike_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 →