Get all available recipes
AI agents call get_recipes to retrieve information from Kitchen MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves static recipe data from the Kitchen MCP Server with no side effects. It matches the Read category definition: 'retrieves or queries data; no side effects (search, list, get, fetch).' The severity is low because exposing recipe data poses minimal security risk—it cannot be misused to cause harm, financial loss, or unintended system changes.
From the tool's definition Tool name 'get_recipes' with description 'Get all available recipes' performs a straightforward data retrieval operation with no modification, deletion, or execution of external operations.
Attacks that exploit this kind of access
Get all available recipes. It is categorised as a Read tool in the Kitchen MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Kitchen MCP Server MCP server in PolicyLayer and add a rule for get_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 Kitchen MCP Server. Nothing to install.
get_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 get_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 get_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.
get_recipes is provided by the Kitchen MCP Server MCP server (paulabaal12/kitchen-mcp). 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 →