Delete weight measurements for a specific date Args: date: Date in YYYY-MM-DD format delete_all: Whether to delete all measurements for the day
AI agents call delete_weigh_ins 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.
This tool permanently removes user health data (weight measurements) from Garmin Connect. The action is irreversible and cannot be undone through the tool's API. While the blast radius is limited to one user's weight history (not system-wide), the destruction of personal health records is a serious consequence if triggered unintentionally by an AI agent.
From the tool's definition Tool name is 'delete_weigh_ins' and description states 'Delete weight measurements for a specific date' with option to 'delete_all' measurements for the day.
Documented attack patterns abuse exactly the kind of access delete_weigh_ins 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_weigh_ins:
{
"version": "1",
"default": "deny",
"hide": [
"delete_weigh_ins"
]
} delete_weigh_ins 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 weight measurements for a specific date Args: date: Date in YYYY-MM-DD format delete_all: Whether to delete all measurements for the day. 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.
Register the Garmin MCP Server MCP server in PolicyLayer and add a rule for delete_weigh_ins: 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.
delete_weigh_ins 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_weigh_ins 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_weigh_ins. 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_weigh_ins 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.
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.