Delete a recipe permanently. Confirm with user before calling.
AI agents call delete_recipe to permanently remove resources in CoupleHub MCP Server — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
This tool irreversibly deletes data (a recipe) and cannot be undone. Destructive is the appropriate category as it is more severe than Write. While the blast radius is somewhat limited (one recipe), the permanent nature of the deletion and lack of recovery mechanism warrants 'high' severity in a shared household context where data loss could cause frustration or loss of important family recipes.
From the tool's definition Tool name is 'delete_recipe' and description states 'Delete a recipe permanently.' The word 'permanently' indicates irreversible data loss.
Attacks that exploit this kind of access
Delete a recipe permanently. Confirm with user before calling. It is categorised as a Destructive tool in the CoupleHub MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the CoupleHub 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 CoupleHub 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 CoupleHub MCP Server MCP server (uczesieweba/couplehub-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 →