Remove a recipe by name. USE WHEN: cleaning up the recipe library. Case-insensitive name matching. Returns confirmation or
AI agents call remove_recipe to permanently remove resources in TilbudsTrolden — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
The tool deletes a recipe from the library. There is no mention of undo, soft delete, or recovery mechanism, making this an irreversible destructive action. Severity is medium since it affects user-created recipe data but is limited in blast radius to the recipe library.
From the tool's definition 'Remove a recipe by name' and 'cleaning up the recipe library' — permanently removes a recipe entry with no indication of reversibility
Documented attack patterns abuse exactly the kind of access remove_recipe gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and TilbudsTrolden, and nothing reaches the server without passing your rules. This is the rule we recommend for remove_recipe:
{
"version": "1",
"default": "deny",
"hide": [
"remove_recipe"
]
} remove_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.
Remove a recipe by name. USE WHEN: cleaning up the recipe library. Case-insensitive name matching. Returns confirmation or. It is categorised as a Destructive tool in the TilbudsTrolden MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the TilbudsTrolden MCP server in PolicyLayer and add a rule for remove_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 TilbudsTrolden. Nothing to install.
remove_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 remove_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 remove_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.
remove_recipe is provided by the TilbudsTrolden MCP server (olgasafonova/tilbudstrolden-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from TilbudsTrolden, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
18 TilbudsTrolden tools catalogued and risk-classified — across an index of 43,000+ MCP servers.