Get detailed information about a specific recipe
AI agents call get_recipe_details to retrieve information from Mcp Cookbook without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and queries recipe information from the Gousto cookbook API. There are no side effects, no data modification, no code execution, and no destructive operations. It is a straightforward read operation that fetches details about a recipe based on an identifier. The low severity reflects that misuse (e.g., retrieving many recipes) poses minimal risk to system integrity or user data.
From the tool's definition Tool name 'get_recipe_details' and description 'Get detailed information about a specific recipe' indicate retrieval of existing data with no modification or execution capability.
Attacks that exploit this kind of access
Get detailed information about a specific recipe. It is categorised as a Read tool in the Mcp Cookbook MCP Server, which means it retrieves data without modifying state.
Register the Mcp Cookbook MCP server in PolicyLayer and add a rule for get_recipe_details: 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 Cookbook. Nothing to install.
get_recipe_details 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_recipe_details 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_recipe_details. 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_recipe_details is provided by the Mcp Cookbook MCP server (springdo/mcp-cookbook). 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 →