Delete weight measurements for a specific date
AI agents call delete_weigh_ins to permanently remove resources in Garmin MCP Server for Poke — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
This tool permanently removes weight measurement records, which cannot be recovered or undone. While the blast radius is limited to a single user's historical health data (not financial or system-critical), deletion of health records is irreversible and represents a destructive operation.
From the tool's definition Tool name is 'delete_weigh_ins' and description states 'Delete weight measurements for a specific date'. The verb 'delete' and the irreversible nature of removing historical health data from Garmin Connect.
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 for Poke MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Garmin MCP Server for Poke 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 for Poke. 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 for Poke MCP server (theol0403/garmin-mcp-poke). 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 →