list_recipe_steps
List all steps in a recipe with their types, connections, and configurations.
This record as markdown: /tools/flowdot-llc-mcp-server/list-recipe-steps.md
What list_recipe_steps does on FlowDot MCP Server
AI agents call list_recipe_steps 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 list_recipe_steps is rated Low
This tool retrieves and displays existing recipe configuration data without modifying, executing, or deleting anything. It has no side effects beyond data retrieval. The blast radius of misuse is minimal—an agent could only access recipe metadata it may not have permission to view, not execute arbitrary code or modify system state.
From the tool's definition Tool name 'list_recipe_steps' and description 'List all steps in a recipe' indicate a retrieval/query operation. The verb 'list' and the passive retrieval nature (no creation, modification, deletion, or execution) clearly position this as a read-only action.
Attacks that exploit this kind of access
The rule that runs list_recipe_steps 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_recipe_steps, this is the rule to start with:
list_recipe_steps 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 list_recipe_steps call is checked against it from then on.
Questions about list_recipe_steps
List all steps in a recipe with their types, connections, and configurations. 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 list_recipe_steps: 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.
list_recipe_steps 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 list_recipe_steps 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 list_recipe_steps. 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.
list_recipe_steps 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