Returns a random Christmas recipe.
AI agents call get_random_recipe to retrieve information from Recettes MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries a database to fetch and return a single recipe entry. It performs no write operations, does not execute code or external operations, and does not delete or modify data. This is a straightforward read operation with minimal blast radius if misused by an agent—the worst outcome would be retrieving unwanted recipe data.
From the tool's definition Tool name 'get_random_recipe' and description 'Returns a random Christmas recipe' indicate a retrieval operation with no side effects. The verb 'Returns' confirms data querying without modification or execution.
Attacks that exploit this kind of access
Returns a random Christmas recipe. It is categorised as a Read tool in the Recettes MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Recettes MCP Server MCP server in PolicyLayer and add a rule for get_random_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 Recettes MCP Server. Nothing to install.
get_random_recipe 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_random_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 get_random_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.
get_random_recipe is provided by the Recettes MCP Server MCP server (symfomany/mcp-tuto). 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 →