fork_recipe
Create a copy of a public recipe into your account. The copy will be private and editable.
This record as markdown: /tools/flowdot-llc-mcp-server/fork-recipe.md
What fork_recipe does on FlowDot MCP Server
AI agents use fork_recipe 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 fork_recipe is rated Medium
This tool creates a new copy of an existing recipe within the user's account space. It is reversible (the copied recipe can be deleted), has no irreversible consequences, does not execute arbitrary code or operations, does not delete data, and has no financial impact. The blast radius of misuse is limited to the user's own workspace. This clearly falls under Write category with low severity.
From the tool's definition Tool description states 'Create a copy of a public recipe into your account.' The verb 'create' and action of copying data into a user's account indicates data creation/modification rather than reading, executing, destructive, or financial operations.
Attacks that exploit this kind of access
The rule that runs fork_recipe 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 fork_recipe, this is the rule to start with:
fork_recipe 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 fork_recipe call is checked against it from then on.
Questions about fork_recipe
Create a copy of a public recipe into your account. The copy will be private and editable. 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 fork_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 FlowDot MCP Server. Nothing to install.
fork_recipe 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 fork_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 fork_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.
fork_recipe 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