Critical Risk →

delete_workout

Delete a workout from Garmin Connect Permanently removes a workout from your Garmin Connect workout library. Args: workout_id: ID of the workout to delete (get IDs from get_workouts)

How to control delete_workout ↓

AI agents call delete_workout to permanently remove resources in Garmin MCP Server — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.

Critical Risk

This tool permanently deletes user fitness data (workouts) from Garmin Connect. Deletion is irreversible and cannot be undone, making it Destructive rather than Write. While a single workout deletion has limited blast radius (high severity rather than critical), the permanent nature of the operation and potential for accidental or malicious bulk deletion of user health records justify this classification.

From the tool's definition Tool name is 'delete_workout' and description explicitly states 'Permanently removes a workout from your Garmin Connect workout library.' The use of 'Permanently removes' and 'Delete' indicates irreversible deletion of user 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 MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for delete_workout:

policy.json
{
  "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.

  1. Create a free account and register Garmin MCP Server — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
RESTRICT THIS TOOL →

Free to start. No card required.

Go deeper

What does the delete_workout tool do? +

Delete a workout from Garmin Connect Permanently removes a workout from your Garmin Connect workout library. Args: workout_id: ID of the workout to delete (get IDs from get_workouts). It is categorised as a Destructive tool in the Garmin MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.

How do I enforce a policy on delete_workout? +

Register the Garmin 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 MCP Server. Nothing to install.

What risk level is delete_workout? +

delete_workout is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.

Can I rate-limit delete_workout? +

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.

How do I block delete_workout completely? +

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.

What MCP server provides delete_workout? +

delete_workout is provided by the Garmin MCP Server MCP server (taxuspt/garmin_mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Garmin MCP Server tool call.

Deterministic rules across all 126 Garmin MCP Server tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

Free to start. No card required.

126 Garmin MCP Server tools catalogued and risk-classified — across an index of 42,500+ MCP servers.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.