get_recipe_version
Fetch the complete definition snapshot of one recipe version. Use this to inspect a prior state before deciding whether to restore_recipe_version. The returned definition matches the shape of get_recipe_definition (steps, stores, entry_step_id, etc.).
This record as markdown: /tools/flowdot-llc-mcp-server/get-recipe-version.md
What get_recipe_version does on FlowDot MCP Server
AI agents call get_recipe_version to retrieve information from FlowDot MCP Server without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why get_recipe_version is rated Low
This tool retrieves historical recipe metadata and configuration data for inspection purposes only. It is a read-only query operation that does not create, modify, delete, or execute any actions. The lowest risk category applies.
From the tool's definition Tool description explicitly states 'Fetch the complete definition snapshot' and 'inspect a prior state' — these are retrieval operations with no modification capability. No side effects are described.
Attacks that exploit this kind of access
The rule that runs get_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 get_recipe_version, this is the rule to start with:
get_recipe_version is read-only, so it stays allowed. 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 get_recipe_version call is checked against it from then on.
Questions about get_recipe_version
Fetch the complete definition snapshot of one recipe version. Use this to inspect a prior state before deciding whether to restore_recipe_version. The returned definition matches the shape of get_recipe_definition (steps, stores, entry_step_id, etc.). It is categorised as a Read tool in the FlowDot MCP Server MCP Server, which means it retrieves data without modifying state.
Register the FlowDot MCP Server MCP server in PolicyLayer and add a rule for get_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.
get_recipe_version is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the get_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 get_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.
get_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