Get training plan workouts for the week containing the given date Returns workouts from your active training plan for the week containing the specified date. The API returns approximately 7 days of scheduled workouts anchored around the given date. Training plan workouts have workout_uuid (not wo...
AI agents call get_training_plan_workouts to retrieve information from Garmin 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 and queries fitness data (scheduled workouts from a training plan) without any side effects. It does not create, modify, delete, or execute operations—it simply returns existing information based on a date parameter. This is a straightforward Read operation with minimal risk from misuse (an agent could only retrieve data the user already has access to).
From the tool's definition Tool description states 'Get training plan workouts' and 'Returns workouts from your active training plan.' The operation is purely retrieval of existing data with no modification, creation, deletion, or execution of external operations.
Documented attack patterns abuse exactly the kind of access get_training_plan_workouts gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Garmin MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for get_training_plan_workouts:
{
"version": "1",
"default": "deny",
"tools": {
"get_training_plan_workouts": {}
}
}get_training_plan_workouts 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 training plan workouts for the week containing the given date Returns workouts from your active training plan for the week containing the specified date. The API returns approximately 7 days of scheduled workouts anchored around the given date. Training plan workouts have workout_uuid (not workout_id). Use the workout_uuid with get_workout_by_id to get detailed step information. Args: calendar_date: Reference date in YYYY-MM-DD format (returns week's workouts). It is categorised as a Read tool in the Garmin MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Garmin MCP Server MCP server in PolicyLayer and add a rule for get_training_plan_workouts: 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 Garmin MCP Server. Nothing to install.
get_training_plan_workouts 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_plan_workouts 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_plan_workouts. 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_plan_workouts is provided by the Garmin MCP Server MCP server (taxuspt/garmin_mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 126 Garmin MCP Server tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
126 Garmin MCP Server tools catalogued and risk-classified — across an index of 42,500+ MCP servers.