Delete a food.
AI agents call mealie_foods_delete to permanently remove resources in Mealie 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 food entries from the Mealie database. Deletion is irreversible and cannot be undone through the tool's normal operations. While the blast radius is scoped to individual food items rather than entire meal plans or recipes, unauthorized or mistaken deletion of foods could disrupt meal planning workflows and shopping list generation.
From the tool's definition Tool name is 'mealie_foods_delete' with description 'Delete a food.' The verb 'delete' combined with the action of removing a food item indicates irreversible data destruction.
Attacks that exploit this kind of access
Delete a food. It is categorised as a Destructive tool in the Mealie MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Mealie MCP Server MCP server in PolicyLayer and add a rule for mealie_foods_delete: 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 Mealie MCP Server. Nothing to install.
mealie_foods_delete 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 mealie_foods_delete 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 mealie_foods_delete. 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.
mealie_foods_delete is provided by the Mealie MCP Server MCP server (mdlopresti/mealie-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 →