run_recipe
Run a built-in worker recipe such as server_quick or network_quick.
This record as markdown: /tools/mcp-control-plane/run-recipe.md
What run_recipe does on Mcp Control Plane
AI agents invoke run_recipe to trigger actions in Mcp Control Plane. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call: builds kicked off, notifications sent, workflows started.
Why run_recipe is rated High
This tool triggers execution of built-in recipes that perform operations on infrastructure (servers, networks). While the specific effects depend on which recipe is invoked, the action itself is to execute/trigger external operations whose consequences are not reversible by the tool itself. This fits the Execute category (runs code, triggers external operations).
From the tool's definition Tool name 'run_recipe' combined with description 'Run a built-in worker recipe such as server_quick or network_quick' indicates execution of pre-defined automation workflows.
Attacks that exploit this kind of access
The rule that runs run_recipe safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Mcp Control Plane, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For run_recipe, this is the rule to start with:
run_recipe stays usable, but rate-capped: a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Mcp Control Plane, apply this rule, and every run_recipe call is checked against it from then on.
Questions about run_recipe
Run a built-in worker recipe such as server_quick or network_quick. It is categorised as a Execute tool in the Mcp Control Plane MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Mcp Control Plane MCP server in PolicyLayer and add a rule for run_recipe: 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 Mcp Control Plane. Nothing to install.
run_recipe is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the run_recipe 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 run_recipe. 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.
run_recipe is provided by the Mcp Control Plane MCP server (albertik322-sudo/mcp-control-plane). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Mcp Control Plane, and thousands of servers like it.
Across the catalogue