delete_recipe_step
Delete a step from a recipe. References to this step will need to be updated.
This record as markdown: /tools/flowdot-llc-mcp-server/delete-recipe-step.md
What delete_recipe_step does on FlowDot MCP Server
AI agents call delete_recipe_step 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_step is rated Critical
This tool permanently removes data (a recipe step) and cannot be undone. While the blast radius is constrained to recipes rather than systemic infrastructure, deletion of workflow steps could break dependent automations or break references in ways difficult to repair. Classified as Destructive rather than Write because deletion is irreversible and alters system state in ways that require manual remediation.
From the tool's definition delete_recipe_step removes a step from a recipe irreversibly; the description explicitly states 'References to this step will need to be updated,' confirming the action has persistent side effects that cascade to dependent entities.
Attacks that exploit this kind of access
The rule that runs delete_recipe_step 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_step, this is the rule to start with:
delete_recipe_step 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_step call is checked against it from then on.
Questions about delete_recipe_step
Delete a step from a recipe. References to this step 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_step: 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_step 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_step 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_step. 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_step 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