Delete a food diary entry by its ID. Args: - food_entry_id: The entry ID to delete Returns: Confirmation of deletion.
AI agents call fatsecret_delete_food_entry to permanently remove resources in Fatsecret — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
This tool permanently removes food diary entries, which cannot be undone. While the blast radius is limited to a user's personal food diary (not financial or system-critical), the irreversible nature of deletion places it in the Destructive category rather than Write.
From the tool's definition Tool name is 'fatsecret_delete_food_entry' and description states 'Delete a food diary entry by its ID' with return of 'Confirmation of deletion.' The verb 'delete' and explicit deletion operation indicate irreversible removal of data.
Attacks that exploit this kind of access
Delete a food diary entry by its ID. Args: - food_entry_id: The entry ID to delete Returns: Confirmation of deletion. It is categorised as a Destructive tool in the Fatsecret MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Fatsecret MCP server in PolicyLayer and add a rule for fatsecret_delete_food_entry: 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 Fatsecret. Nothing to install.
fatsecret_delete_food_entry 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 fatsecret_delete_food_entry 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 fatsecret_delete_food_entry. 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.
fatsecret_delete_food_entry is provided by the Fatsecret MCP server (yurzs/fatsecret-mcp-server). 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 →