list_shared_recipe_runs

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/list-shared-recipe-runs.md

WHAT IT DOES

What list_shared_recipe_runs does on FlowDot MCP Server

AI agents call list_shared_recipe_runs 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.

RISK

Why list_shared_recipe_runs is rated Low

This tool only retrieves and lists existing data (published recipe runs, snapshots of executions). It has no side effects, does not create, modify, or delete anything. It is a pure read/query operation with minimal blast radius.

From the tool's definition List published runs for a recipe... Use this to discover community runs, compare models a recipe has been run with, or find runs to bundle into a benchmark.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs list_shared_recipe_runs 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 list_shared_recipe_runs, this is the rule to start with:

list_shared_recipe_runs Allowed

list_shared_recipe_runs is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "list_shared_recipe_runs": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect FlowDot MCP Server, apply this rule, and every list_shared_recipe_runs call is checked against it from then on.

FAQ

Questions about list_shared_recipe_runs

What does the list_shared_recipe_runs tool do? +

List published runs for a recipe. Each run is a frozen snapshot of one execution including total tokens, duration, model lineup, and the final output stores. Use this to discover community runs, compare models a recipe has been run with, or find runs to bundle into a benchmark. 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 list_shared_recipe_runs? +

Register the FlowDot MCP Server MCP server in PolicyLayer and add a rule for list_shared_recipe_runs: 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 list_shared_recipe_runs? +

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

Can I rate-limit list_shared_recipe_runs? +

Yes. Add a rate_limit block to the list_shared_recipe_runs 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 list_shared_recipe_runs completely? +

Set action: deny in the PolicyLayer policy for list_shared_recipe_runs. 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 list_shared_recipe_runs? +

list_shared_recipe_runs 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.

KEEP EXPLORING

More on FlowDot MCP Server, and thousands of servers like it.

This server

All 207 FlowDot MCP Server tools →

Across the catalogue

aiva_list_affiliates on AIVA MCP Server →list_agents on 0rca Dojo MCP Server → The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →