Log health metrics (weight, HRV, sleep, steps, etc.) for a date.
AI agents use tp_log_metrics 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.
This tool writes health metric data to TrainingPeaks for a specific date. It creates new records but is reversible in principle (entries can be updated or deleted). No financial, destructive, or execution risk is present. Misuse could result in incorrect health/training data being logged, affecting training recommendations, hence medium severity.
From the tool's definition 'Log health metrics (weight, HRV, sleep, steps, etc.) for a date' — creates/records new health data entries
Attacks that exploit this kind of access
Log health metrics (weight, HRV, sleep, steps, etc.) for a date. 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_log_metrics: 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_log_metrics 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_log_metrics 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_log_metrics. 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_log_metrics 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 →