Get a list of recipes from a specific category
AI agents call get_recipes_by_category 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 data based on category filters. It has no side effects, does not modify or delete data, does not execute code, and does not involve financial transactions. It is a straightforward read operation consistent with search/list/get/fetch operations. Severity is low because misuse (e.g., retrieving all recipes) poses minimal risk to the system or user.
From the tool's definition Tool name 'get_recipes_by_category' and description 'Get a list of recipes from a specific category' indicate data retrieval with no modification, deletion, or execution of external operations.
Attacks that exploit this kind of access
Get a list of recipes from a specific category. 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_recipes_by_category: 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_recipes_by_category 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_by_category 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_by_category. 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_by_category 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 →