Delete a workout from Garmin Connect by its ID.
AI agents call delete_workout to permanently remove resources in Garmin — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
This tool permanently removes workout records from a user's Garmin Connect account. Deletion is irreversible and cannot be undone. While the blast radius is limited to the user's own fitness data (not financial systems or critical infrastructure), accidental or malicious deletion of workout history represents a significant loss of personal health records.
From the tool's definition Tool name is 'delete_workout' with description 'Delete a workout from Garmin Connect by its ID.' The verb 'delete' indicates irreversible removal of data.
Attacks that exploit this kind of access
Delete a workout from Garmin Connect by its ID. It is categorised as a Destructive tool in the Garmin MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Garmin 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. 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 MCP server (marcelohensantos/garmin-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 →