start-recipe
AI agents invoke start-recipe to trigger actions in Workato MCP Server. 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.
Although the description is empty, the tool name combined with server context indicates this tool executes/runs a recipe (Workato's term for automated workflows/integrations). This is an Execute category tool because it triggers external operations and workflow executions whose side effects depend on what the recipe does.
From the tool's definition Tool name is 'start-recipe' in the context of a Workato MCP Server that manages recipes (automated workflows). Starting a recipe triggers execution of a workflow whose effects depend on the recipe's configuration and logic.
Attacks that exploit this kind of access
start-recipe. It is categorised as a Execute tool in the Workato MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Workato MCP Server MCP server in PolicyLayer and add a rule for start-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 Workato MCP Server. Nothing to install.
start-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 start-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 start-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.
start-recipe is provided by the Workato MCP Server MCP server (jacobgoren-sb/workato-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →