Get athlete settings: FTP, thresholds, zones, profile.
AI agents call tp_get_athlete_settings 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 existing athlete settings and performance metrics (FTP, thresholds, zones, profile). It performs a query operation with no capability to modify, delete, execute commands, or trigger financial transactions. The action is read-only and non-destructive, making it a Read category tool with low severity risk.
From the tool's definition Tool name 'tp_get_athlete_settings' and description 'Get athlete settings: FTP, thresholds, zones, profile' indicate retrieval of configuration/profile data with no modification or side effects.
Attacks that exploit this kind of access
Get athlete settings: FTP, thresholds, zones, profile. 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_athlete_settings: 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_athlete_settings 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_athlete_settings 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_athlete_settings. 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_athlete_settings 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 →