List workouts in date range. Query only days needed. Max 90 days.
AI agents call tp_get_workouts 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/queries workout data within a specified date range with no side effects. It performs a straightforward data retrieval operation with built-in safeguards (90-day maximum), consistent with the 'Read' category. The low severity reflects minimal risk from accidental misuse by an AI agent querying fitness data.
From the tool's definition Tool name contains 'get' and description states 'List workouts' with no mention of modification, deletion, or execution capabilities. The constraint 'Query only days needed. Max 90 days' indicates a simple retrieval operation.
Attacks that exploit this kind of access
List workouts in date range. Query only days needed. Max 90 days. 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_workouts: 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_workouts 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_workouts 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_workouts. 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_workouts 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 →