Delete weight measurements for a specific date
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 health data (weight measurements) that cannot be easily recovered. While the blast radius is constrained to a single user's weight history and not system-critical or financial, it represents irreversible data loss. Destructive category applies because the operation cannot be undone through normal API operations.
From the tool's definition Tool name contains 'delete' and description states 'Delete weight measurements for a specific date' — explicit irreversible data removal.
Attacks that exploit this kind of access
Delete weight measurements for a specific date. 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 (jbaker48/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 →