Delete one household cookbook by ID.
AI agents call delete_cookbook 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 a cookbook resource without the ability to undo the action. Deletion operations that cannot be reversed fall squarely into the Destructive category. The severity is high because loss of a household cookbook could affect meal planning and recipes for multiple users, though the blast radius is limited to a single cookbook rather than system-wide data.
From the tool's definition Tool name 'delete_cookbook' and description 'Delete one household cookbook by ID' explicitly indicate irreversible deletion of data.
Attacks that exploit this kind of access
Delete one household cookbook by ID. 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_cookbook: 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_cookbook 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_cookbook 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_cookbook. 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_cookbook 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 →