Delete an activity permanently. This action cannot be undone
AI agents call delete_activity to permanently remove resources in Garmin Connect — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
This tool permanently removes user health/fitness data with no recovery option. The irreversible deletion of personal records constitutes a destructive action. While the blast radius is limited to a single user's Garmin account, the permanent loss of fitness history and training records represents significant harm if invoked incorrectly by an AI agent.
From the tool's definition Tool description explicitly states: 'Delete an activity permanently. This action cannot be undone'
Documented attack patterns abuse exactly the kind of access delete_activity gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Garmin Connect, and nothing reaches the server without passing your rules. This is the rule we recommend for delete_activity:
{
"version": "1",
"default": "deny",
"hide": [
"delete_activity"
]
}delete_activity 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 an activity permanently. This action cannot be undone. It is categorised as a Destructive tool in the Garmin Connect MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Garmin Connect MCP server in PolicyLayer and add a rule for delete_activity: 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 Connect. Nothing to install.
delete_activity 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_activity 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_activity. 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_activity is provided by the Garmin Connect MCP server (nicolasvegam/garmin-connect-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 97 Garmin Connect tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
97 Garmin Connect tools catalogued and risk-classified — across an index of 42,500+ MCP servers.