Delete a cookbook.
AI agents call mealie_cookbooks_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.
The tool permanently deletes a cookbook, which is a destructive action that cannot be undone. Even though the blast radius is limited to cookbook data rather than critical system data, the irreversible nature of deletion places it in the Destructive category with high severity. An AI agent misusing this could remove user-curated cookbooks without recovery options.
From the tool's definition Tool name contains 'delete' and description states 'Delete a cookbook.' This is an irreversible operation that removes data.
Attacks that exploit this kind of access
Delete a cookbook. 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_cookbooks_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_cookbooks_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_cookbooks_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_cookbooks_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_cookbooks_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 →