delete_recipe_store
Delete a store from a recipe. Steps using this store will need to be updated.
This record as markdown: /tools/flowdot-llc-mcp-server/delete-recipe-store.md
What delete_recipe_store does on FlowDot MCP Server
AI agents call delete_recipe_store to permanently remove resources in FlowDot MCP Server, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Why delete_recipe_store is rated Critical
This tool irreversibly deletes data (a recipe store) and creates a breaking change for dependent workflow steps. This is destructive rather than merely write-level because deletion cannot be undone and impacts other system components. The high severity reflects the blast radius of an AI agent accidentally deleting critical recipe stores that other workflows depend on.
From the tool's definition The tool name explicitly contains 'delete' and the description states it will 'Delete a store from a recipe' with cascading consequences ('Steps using this store will need to be updated'), indicating irreversible data removal.
Attacks that exploit this kind of access
The rule that runs delete_recipe_store safely
PolicyLayer is an MCP gateway: it sits between your AI agents and FlowDot MCP Server, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For delete_recipe_store, this is the rule to start with:
delete_recipe_store is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.
The button opens the PolicyLayer dashboard: create your workspace, connect FlowDot MCP Server, apply this rule, and every delete_recipe_store call is checked against it from then on.
Questions about delete_recipe_store
Delete a store from a recipe. Steps using this store will need to be updated. It is categorised as a Destructive tool in the FlowDot MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the FlowDot MCP Server MCP server in PolicyLayer and add a rule for delete_recipe_store: 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 FlowDot MCP Server. Nothing to install.
delete_recipe_store 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_store 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_store. 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_store is provided by the FlowDot MCP Server MCP server (flowdot-llc/mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on FlowDot MCP Server, and thousands of servers like it.
Across the catalogue