Delete a recipe from Paprika by moving it to trash. REQUIRES CONFIRMATION. Provide either uid or title to identify the recipe, then call again with confirm=true to proceed with deletion.
AI agents call delete_recipe to permanently remove resources in Paprika — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
This tool performs irreversible deletion of recipe data. Although it moves to trash rather than permanent hard delete, the user-facing effect is data loss that cannot be recovered without restore capabilities. This is the most severe category applicable (Destructive > Execute > Write > Read).
From the tool's definition Tool description explicitly states 'Delete a recipe from Paprika by moving it to trash' and requires confirmation before permanent removal. The action irreversibly removes data (recipes) from the system.
Attacks that exploit this kind of access
Delete a recipe from Paprika by moving it to trash. REQUIRES CONFIRMATION. Provide either uid or title to identify the recipe, then call again with confirm=true to proceed with deletion. It is categorised as a Destructive tool in the Paprika MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Paprika 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 Paprika. 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 Paprika MCP server (sandordaroczi/paprika-mcp-python-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
delete_recipe is one line of Paprika's registry record.
The record carries the whole server: verified identity, auth posture, risk grade, every tool classified, recommended policy — re-checked continuously.
Teams ship this data inside their own products. See what a licence covers →