Upload a workout file (.fit, .tcx, .gpx) to an existing workout.
AI agents use tp_upload_workout_file to create or update resources in TrainingPeaks-MCP — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your TrainingPeaks-MCP environment.
The tool creates or attaches new workout file data to an existing workout record, which is a reversible modification operation. This is a Write action rather than Read (retrieves data), Execute (runs arbitrary commands), Destructive (irreversibly deletes), or Financial.
From the tool's definition Tool name contains 'upload' and description states 'Upload a workout file (.fit, .tcx, .gpx) to an existing workout', indicating creation or modification of data associated with a workout record.
Attacks that exploit this kind of access
Upload a workout file (.fit, .tcx, .gpx) to an existing workout. It is categorised as a Write tool in the TrainingPeaks-MCP MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the TrainingPeaks- MCP server in PolicyLayer and add a rule for tp_upload_workout_file: 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 TrainingPeaks-MCP. Nothing to install.
tp_upload_workout_file 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 tp_upload_workout_file 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 tp_upload_workout_file. 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.
tp_upload_workout_file is provided by the TrainingPeaks- MCP server (jamsusmaximus/trainingpeaks-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 →