Create a steady Z2 walking workout and upload it to Garmin Connect. Args: name: Workout name duration_min: Main walking block duration in minutes hr_min: Minimum heart rate in bpm (used for description; target is Z2) hr_max: Maximum heart rate in bpm (used for description; target is Z2)
AI agents use create_z2_walk_workout 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 and writes new workout data to Garmin Connect. It is reversible (the workout can be edited or deleted later), has no external side effects beyond data storage, and does not execute arbitrary code or delete data. The blast radius of misuse is limited to creating unwanted fitness records in the user's account, which is a low-severity impact.
From the tool's definition Tool description states 'Create a steady Z2 walking workout and upload it to Garmin Connect' — the verb 'create' and 'upload' indicate data creation/modification.
Documented attack patterns abuse exactly the kind of access create_z2_walk_workout 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 create_z2_walk_workout:
{
"version": "1",
"default": "deny",
"tools": {
"create_z2_walk_workout": {
"limits": [
{
"counter": "create_z2_walk_workout_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}create_z2_walk_workout 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.
Create a steady Z2 walking workout and upload it to Garmin Connect. Args: name: Workout name duration_min: Main walking block duration in minutes hr_min: Minimum heart rate in bpm (used for description; target is Z2) hr_max: Maximum heart rate in bpm (used for description; target is Z2). 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 create_z2_walk_workout: 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.
create_z2_walk_workout 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 create_z2_walk_workout 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 create_z2_walk_workout. 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.
create_z2_walk_workout 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.