Remove a previously logged food entry by its logId (from log_food or log_meal_photo output). Use this to undo a mistake.
AI agents call delete_food_log to permanently remove resources in Fitbit Googlehealth — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
This tool irreversibly deletes health records (food log entries) from the user's Fitbit account. Deletion cannot be undone, making it Destructive rather than Write. While the blast radius is somewhat limited to nutrition data (not financial or system-critical), deletion of personal health records represents a high-severity risk if an AI agent misuses it through argument injection or confused intent.
From the tool's definition Tool name is 'delete_food_log' and description states 'Remove a previously logged food entry' and 'Use this to undo a mistake' — explicit deletion operation on user health data.
Attacks that exploit this kind of access
Remove a previously logged food entry by its logId (from log_food or log_meal_photo output). Use this to undo a mistake. It is categorised as a Destructive tool in the Fitbit Googlehealth MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Fitbit Googlehealth 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 Fitbit Googlehealth. 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 Fitbit Googlehealth MCP server (tachibanayu24/fitbit-googlehealth-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 →