This record as markdown: /tools/flowdot-llc-mcp-server/update-recipe-store.md
What update_recipe_store does on FlowDot MCP Server
AI agents use update_recipe_store to create or update resources in FlowDot MCP Server, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your FlowDot MCP Server environment.
Why update_recipe_store is rated Medium
The tool creates or modifies data reversibly within FlowDot's recipe store. While the description is minimal ('Update a store'), the verb 'update' and context of recipe management on a workflow platform suggest this is a Write operation that alters existing records. Confidence is not higher due to the vague description, which does not detail what 'store' means or what constraints exist on updates.
From the tool's definition Tool name 'update_recipe_store' and description 'Update a store' indicate modification of data within the recipe store without deletion capability.
Attacks that exploit this kind of access
The rule that runs update_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 update_recipe_store, this is the rule to start with:
update_recipe_store stays usable, but capped: an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect FlowDot MCP Server, apply this rule, and every update_recipe_store call is checked against it from then on.
Questions about update_recipe_store
Update a store. It is categorised as a Write tool in the FlowDot MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the FlowDot MCP Server MCP server in PolicyLayer and add a rule for update_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.
update_recipe_store is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the update_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 update_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.
update_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.
This server
Across the catalogue