get_training_calendar
AI agents call get_training_calendar 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 training calendar data from Garmin Connect, consistent with other 'get_' prefixed tools on the server that query personal fitness metrics and activity data. No side effects, modifications, deletions, or external operations are implied. The blast radius of misuse is minimal—an AI agent could only access the user's own training calendar data, not modify it or cause harm.
From the tool's definition Tool name 'get_training_calendar' indicates a retrieval operation. All sibling tools on the server (get_activities, get_activity_zones, get_bike_session, etc.) follow a consistent 'get_*' pattern reflecting read-only data retrieval from Garmin Connect.
Attacks that exploit this kind of access
get_training_calendar. 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_training_calendar: 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_training_calendar 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_training_calendar 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_training_calendar. 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_training_calendar 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 →