Critical Risk →

delete_workouts

Delete multiple workouts from Garmin Connect in a single call Permanently removes multiple workouts from your Garmin Connect workout library. Args: workout_ids: List of workout IDs to delete (get IDs from get_workouts)

How to control delete_workouts ↓

AI agents call delete_workouts 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 irreversibly deletes user fitness data (workouts) from Garmin Connect. Deletion cannot be undone, which is the defining characteristic of the Destructive category. While the blast radius is limited to the user's own workout data (not financial or system-wide), the permanent nature and inability to recover deleted workouts warrants high severity.

From the tool's definition Tool name 'delete_workouts' and description states 'Permanently removes multiple workouts from your Garmin Connect workout library.' The use of 'permanently' and 'removes' indicates irreversible deletion of user data.

Documented attack patterns abuse exactly the kind of access delete_workouts 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_workouts:

policy.json
{
  "version": "1",
  "default": "deny",
  "hide": [
    "delete_workouts"
  ]
}

delete_workouts 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_workouts tool do? +

Delete multiple workouts from Garmin Connect in a single call Permanently removes multiple workouts from your Garmin Connect workout library. Args: workout_ids: List of workout IDs 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_workouts? +

Register the Garmin MCP Server MCP server in PolicyLayer and add a rule for delete_workouts: 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_workouts? +

delete_workouts 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_workouts? +

Yes. Add a rate_limit block to the delete_workouts 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_workouts completely? +

Set action: deny in the PolicyLayer policy for delete_workouts. 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_workouts? +

delete_workouts 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.