Delete a meal plan entry.
AI agents call delete_meal_plan_entry 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.
The tool performs an irreversible deletion of meal plan data. Destructive actions rank above Execute because they cannot be undone. While the blast radius is limited to a single meal plan entry (not system-wide), unauthorized deletion of user meal plans could disrupt dietary planning and food preparation.
From the tool's definition Tool name explicitly states 'delete' and description confirms 'Delete a meal plan entry' — this operation irreversibly removes data from the meal plan without possibility of reversal.
Attacks that exploit this kind of access
Delete a meal plan entry. 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 delete_meal_plan_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 Mealie MCP Server. Nothing to install.
delete_meal_plan_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 delete_meal_plan_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 delete_meal_plan_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.
delete_meal_plan_entry is provided by the Mealie MCP Server MCP server (nikopol666/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 →