Delete a recipe permanently. Args: slug: The unique text identifier for the recipe to delete. Returns: Dict[str, Any]: Confirmation of deletion.
AI agents call delete_recipe 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 deletes recipe data from the database with no undo mechanism. While the blast radius is somewhat limited to a single recipe record rather than bulk deletion, the irreversible nature of permanent deletion places it in the Destructive category, which outranks Write or Execute.
From the tool's definition Tool name 'delete_recipe' and description 'Delete a recipe permanently' explicitly indicate irreversible deletion of data.
Documented attack patterns abuse exactly the kind of access delete_recipe gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Mealie MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for delete_recipe:
{
"version": "1",
"default": "deny",
"hide": [
"delete_recipe"
]
} delete_recipe 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 recipe permanently. Args: slug: The unique text identifier for the recipe to delete. Returns: Dict[str, Any]: Confirmation of deletion. 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_recipe: 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_recipe 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_recipe 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_recipe. 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_recipe is provided by the Mealie MCP Server MCP server (rldiao/mealie-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 44 Mealie MCP Server tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
44 Mealie MCP Server tools catalogued and risk-classified — across an index of 42,500+ MCP servers.