Upload a workout from JSON data
AI agents use upload_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 or modifies fitness workout records in Garmin Connect, which is a reversible operation (workouts can be edited or removed later). It does not execute arbitrary code, delete data irreversibly, or move money. The blast radius is medium because a misused upload could pollute a user's fitness history with incorrect workouts, but the impact is limited to the user's own data and is recoverable.
From the tool's definition Tool is named 'upload_workout' and described as 'Upload a workout from JSON data'. The verb 'upload' indicates creation/modification of data on the Garmin platform.
Attacks that exploit this kind of access
Upload a workout from JSON data. 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 upload_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.
upload_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 upload_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 upload_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.
upload_workout is provided by the Garmin MCP Server MCP server (jbaker48/garmin-mcp). 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 →