Remove an availability entry.
AI agents call tp_delete_availability to permanently remove resources in TrainingPeaks-MCP — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
This tool permanently removes availability entries without the ability to undo the action. Even though the blast radius is limited to scheduling/availability data rather than critical systems, deletion is irreversible and represents data loss. It is more severe than Write operations (which are reversible via updates) but less severe than financial impacts.
From the tool's definition Tool name is 'tp_delete_availability' with description 'Remove an availability entry.' The verb 'delete' and 'remove' indicate irreversible deletion of data.
Attacks that exploit this kind of access
Remove an availability entry. It is categorised as a Destructive tool in the TrainingPeaks-MCP MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the TrainingPeaks- MCP server in PolicyLayer and add a rule for tp_delete_availability: 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_delete_availability is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the tp_delete_availability 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_delete_availability. 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_delete_availability 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 →