get_shared_recipe_run
Get full details of one published recipe run: per-step trace (model, tokens, duration, tool calls), total tokens, speculative cost from current model pricing, and the final output stores. Use this to compare runs in detail or read the actual answer a recipe produced.
This record as markdown: /tools/flowdot-llc-mcp-server/get-shared-recipe-run.md
What get_shared_recipe_run does on FlowDot MCP Server
AI agents call get_shared_recipe_run 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_shared_recipe_run is rated Low
This tool retrieves and queries historical data about published recipe runs. It is purely informational—fetching execution traces, token counts, costs, and outputs for analysis and comparison. There are no side effects, data modifications, or external operations triggered. This is a straightforward Read operation.
From the tool's definition Tool description states it "Get[s] full details" and "read[s] the actual answer a recipe produced" — these are retrieval operations with no side effects.
Attacks that exploit this kind of access
The rule that runs get_shared_recipe_run 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_shared_recipe_run, this is the rule to start with:
get_shared_recipe_run 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_shared_recipe_run call is checked against it from then on.
Questions about get_shared_recipe_run
Get full details of one published recipe run: per-step trace (model, tokens, duration, tool calls), total tokens, speculative cost from current model pricing, and the final output stores. Use this to compare runs in detail or read the actual answer a recipe produced. 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_shared_recipe_run: 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_shared_recipe_run 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_shared_recipe_run 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_shared_recipe_run. 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_shared_recipe_run 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