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.

SERVERFlowDot MCP Server SOURCEflowdot-llc/mcp-server
Low RISK CLASS
Category Read
Parameters 00 required
Recommended Allowedsee the rule below
Registry record Grade F, identity unverified Pull the record →

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.

Questions about get_shared_recipe_run

What does the get_shared_recipe_run tool do? +

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.

How do I enforce a policy on get_shared_recipe_run? +

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.

What risk level is get_shared_recipe_run? +

get_shared_recipe_run is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit get_shared_recipe_run? +

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.

How do I block get_shared_recipe_run completely? +

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.

What MCP server provides get_shared_recipe_run? +

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.

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of FlowDot MCP Server's. Pull the full record:

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.