list-recipes
AI agents call list-recipes to retrieve information from Workato MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
List operations retrieve and display data without modifying state. The tool retrieves recipe information from Workato, which has no side effects beyond data access. Low severity because querying recipes poses minimal risk even if an AI misuses the tool—it can only expose existing recipe metadata, not execute or modify them.
From the tool's definition Tool name 'list-recipes' with context that it's part of Workato MCP Server for 'management of recipes'. The 'list-' prefix and sibling tools like 'list-activity-logs', 'list-all-connectors', and 'list-connections' all indicate query/retrieval operations.
Attacks that exploit this kind of access
list-recipes. It is categorised as a Read tool in the Workato MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Workato MCP Server MCP server in PolicyLayer and add a rule for list-recipes: 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.
list-recipes 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-recipes 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-recipes. 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-recipes 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 →