Delete a workout from Garmin Connect.
AI agents call delete_workout to permanently remove resources in Garmin Workouts MCP Server — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Deletion of workout data cannot be undone and removes user-created content permanently. While not as critical as financial or system-level destruction, accidental or malicious deletion of user fitness data represents a significant loss. This is classified as Destructive rather than Write because the operation is irreversible and the effect is permanent data loss.
From the tool's definition Tool name is 'delete_workout' and description states 'Delete a workout from Garmin Connect.' The verb 'delete' indicates irreversible removal of data.
Documented attack patterns abuse exactly the kind of access delete_workout gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Garmin Workouts MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for delete_workout:
{
"version": "1",
"default": "deny",
"hide": [
"delete_workout"
]
} delete_workout disappears from the agent's tool list entirely, and any attempt to call it is denied. The rest of the server keeps working.
Free to start. No card required.
Delete a workout from Garmin Connect. It is categorised as a Destructive tool in the Garmin Workouts MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Garmin Workouts MCP Server MCP server in PolicyLayer and add a rule for delete_workout: 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 Garmin Workouts MCP Server. Nothing to install.
delete_workout 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 delete_workout 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 delete_workout. 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.
delete_workout is provided by the Garmin Workouts MCP Server MCP server (st3v/garmin-workouts-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Garmin Workouts MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
10 Garmin Workouts MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.