Unpair a workout. Detaches the completed workout file from the
AI agents use tp_unpair_workout 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.
Unpairing/detaching a workout file is a reversible modification (the workout and file still exist, just dissociated), making this a Write operation. It is not truly Destructive since neither the workout nor the file is deleted. Confidence is moderate due to the truncated description leaving some ambiguity about full effects.
From the tool's definition 'Unpair a workout. Detaches the completed workout file from the' — description is truncated but indicates detaching/unlinking a workout file association
Attacks that exploit this kind of access
Unpair a workout. Detaches the completed workout file from the. 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_unpair_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 TrainingPeaks-MCP. Nothing to install.
tp_unpair_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 tp_unpair_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 tp_unpair_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.
tp_unpair_workout 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 →