delete_recipe_store

Delete a store from a recipe. Steps using this store will need to be updated.

SERVERFlowDot MCP Server SOURCEflowdot-llc/mcp-server
Critical RISK CLASS
Category Destructive
Parameters 00 required
Recommended Hiddensee the rule below
Registry record Grade F, identity unverified Pull the record →

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.

Questions about delete_recipe_store

What does the delete_recipe_store tool do? +

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.

How do I enforce a policy on delete_recipe_store? +

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.

What risk level is delete_recipe_store? +

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.

Can I rate-limit delete_recipe_store? +

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.

How do I block delete_recipe_store completely? +

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.

What MCP server provides delete_recipe_store? +

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.

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of FlowDot MCP Server's. Pull the full record:

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.