get_recipe_benchmark
Get a published recipe benchmark with all of its grouped runs side-by-side. Each run carries totals, model lineup per step, and speculative cost computed from current model pricing. Use this to compare configurations on the same recipe and reason about cost/quality tradeoffs.
This record as markdown: /tools/flowdot-llc-mcp-server/get-recipe-benchmark.md
What get_recipe_benchmark does on FlowDot MCP Server
AI agents call get_recipe_benchmark 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_benchmark is rated Low
This tool retrieves and presents existing benchmark data for analysis and comparison purposes. It performs a read-only query operation with no side effects—it does not create, modify, delete, or execute anything.
From the tool's definition Tool description explicitly states 'Get a published recipe benchmark' and describes retrieving and viewing performance data, runs, model information, and cost computations. No modification, deletion, or execution of operations is indicated.
Attacks that exploit this kind of access
The rule that runs get_recipe_benchmark 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_benchmark, this is the rule to start with:
get_recipe_benchmark 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_benchmark call is checked against it from then on.
Questions about get_recipe_benchmark
Get a published recipe benchmark with all of its grouped runs side-by-side. Each run carries totals, model lineup per step, and speculative cost computed from current model pricing. Use this to compare configurations on the same recipe and reason about cost/quality tradeoffs. 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_benchmark: 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_benchmark 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_benchmark 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_benchmark. 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_benchmark 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