Get workout details by ID. Use after tp_get_workouts.
AI agents call tp_get_workout to retrieve information from TrainingPeaks-MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves workout information by identifier without creating, modifying, deleting, or executing any actions. It is a simple query operation with no blast radius if misused—it can only expose fitness data that the authenticated user would have access to anyway. The low severity reflects the read-only nature and limited potential for harm through misuse.
From the tool's definition Tool name 'tp_get_workout' and description 'Get workout details by ID' clearly indicate data retrieval with no side effects. The verb 'Get' and the pattern of querying existing workout data are characteristic of Read operations.
Attacks that exploit this kind of access
Get workout details by ID. Use after tp_get_workouts. It is categorised as a Read tool in the TrainingPeaks-MCP MCP Server, which means it retrieves data without modifying state.
Register the TrainingPeaks- MCP server in PolicyLayer and add a rule for tp_get_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_get_workout is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the tp_get_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_get_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_get_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 →