Schedule a list of workouts for the week in a single call. Idempotent: if a workout is already scheduled for that date, it is reported as already scheduled and the POST is skipped (avoids duplicating calendar entries). Args: week: List of dicts with keys: date (YYYY-MM-DD), workout_id (int)
AI agents use schedule_week to create or update resources in Garmin MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Garmin MCP Server environment.
This tool creates or modifies workout schedule entries in Garmin Connect, which is reversible (workouts can be unscheduled or rescheduled). It does not execute arbitrary code, delete data irreversibly, or involve financial transactions.
From the tool's definition Tool description states it 'Schedule a list of workouts for the week' and mentions 'POST' operation, indicating it creates calendar entries.
Documented attack patterns abuse exactly the kind of access schedule_week 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 schedule_week:
{
"version": "1",
"default": "deny",
"tools": {
"schedule_week": {
"limits": [
{
"counter": "schedule_week_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}schedule_week stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Schedule a list of workouts for the week in a single call. Idempotent: if a workout is already scheduled for that date, it is reported as already scheduled and the POST is skipped (avoids duplicating calendar entries). Args: week: List of dicts with keys: date (YYYY-MM-DD), workout_id (int). It is categorised as a Write tool in the Garmin MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Garmin MCP Server MCP server in PolicyLayer and add a rule for schedule_week: 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.
schedule_week is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the schedule_week 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 schedule_week. 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.
schedule_week 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.