restore_recipe_version
Restore a recipe to one of its prior versions. The current state is automatically snapshotted before the restore applies, so this action is reversible — call restore_recipe_version again on the
This record as markdown: /tools/flowdot-llc-mcp-server/restore-recipe-version.md
What restore_recipe_version does on FlowDot MCP Server
AI agents use restore_recipe_version 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 restore_recipe_version is rated Medium
This tool creates a modification to existing data (the recipe's current state) by reverting it to a historical version. While technically reversible due to automatic snapshotting, it irreversibly changes the active recipe configuration at the time of execution.
From the tool's definition The tool 'restore_recipe_version' performs a versioning/rollback operation that modifies the current state of a recipe by replacing it with a prior version.
Attacks that exploit this kind of access
The rule that runs restore_recipe_version 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 restore_recipe_version, this is the rule to start with:
restore_recipe_version 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 restore_recipe_version call is checked against it from then on.
Questions about restore_recipe_version
Restore a recipe to one of its prior versions. The current state is automatically snapshotted before the restore applies, so this action is reversible — call restore_recipe_version again on the. 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 restore_recipe_version: 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.
restore_recipe_version 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 restore_recipe_version 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 restore_recipe_version. 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.
restore_recipe_version 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