Update an event.
AI agents use tp_update_event 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 modifies event data within the TrainingPeaks fitness platform. While updates are reversible (the prior state is not permanently lost and can be corrected), they represent data modification with potential side effects if an AI agent updates events incorrectly—such as changing event dates, details, or metadata that users rely on.
From the tool's definition Tool name 'tp_update_event' and description 'Update an event' indicate modification of existing data. The verb 'update' is a reversible write operation that modifies but does not delete event records.
Attacks that exploit this kind of access
Update an event. 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_update_event: 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_update_event 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_update_event 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_update_event. 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_update_event 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 →