Delete a food log entry Permanently removes a logged food item from the nutrition log. Use get_nutrition_daily_food_log to find the logId of the entry to delete. Args: log_id: Log entry ID to delete (from get_nutrition_daily_food_log)
AI agents call delete_food_log 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 and irreversibly deletes nutrition log entries. Destructive actions that cannot be undone rank higher than Write (which is reversible) or Read. While the blast radius is limited to a single user's nutrition data (not system-wide or financial), the permanent nature of deletion and lack of recovery mechanism classifies it as Destructive with high severity, as misuse could cause loss of important…
From the tool's definition 'Permanently removes a logged food item from the nutrition log' and 'Delete a food log entry' — the tool irreversibly deletes user data without the ability to undo the action.
Documented attack patterns abuse exactly the kind of access delete_food_log 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_food_log:
{
"version": "1",
"default": "deny",
"hide": [
"delete_food_log"
]
}delete_food_log 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 a food log entry Permanently removes a logged food item from the nutrition log. Use get_nutrition_daily_food_log to find the logId of the entry to delete. Args: log_id: Log entry ID to delete (from get_nutrition_daily_food_log). 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_food_log: 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_food_log 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_food_log 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_food_log. 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_food_log 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.