Low Risk

get_recipe_details

Retrieve the full details of a specific recipe.

How to control get_recipe_details ↓

What get_recipe_details does on Tandoor MCP Server

AI agents call get_recipe_details to retrieve information from Tandoor MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Low Risk

Why get_recipe_details needs a policy

This tool retrieves existing recipe data without creating, modifying, deleting, or executing any operations. It is a pure read operation that queries the Tandoor recipe database. The blast radius of misuse is minimal—at worst, an agent could retrieve recipes it shouldn't have access to, but no data destruction, financial impact, or code execution is possible.

From the tool's definition Tool name 'get_recipe_details' and description 'Retrieve the full details of a specific recipe' indicate a retrieval operation with no modification or side effects.

Documented attack patterns abuse exactly the kind of access get_recipe_details gives an agent:

How to control get_recipe_details

PolicyLayer is an MCP gateway — it sits between your AI agents and Tandoor MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for get_recipe_details:

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "get_recipe_details": {}
  }
}

get_recipe_details is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.

  1. Create a free account and register Tandoor MCP Server — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
CAP THIS TOOL →

Free to start. No card required.

Related tools and policies

Go deeper

Questions about get_recipe_details

What does the get_recipe_details tool do? +

Retrieve the full details of a specific recipe. It is categorised as a Read tool in the Tandoor MCP Server MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get_recipe_details? +

Register the Tandoor MCP Server 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 Tandoor MCP Server. Nothing to install.

What risk level is get_recipe_details? +

get_recipe_details is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit get_recipe_details? +

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.

How do I block get_recipe_details completely? +

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.

What MCP server provides get_recipe_details? +

get_recipe_details is provided by the Tandoor MCP Server MCP server (starbuck93/tandoor-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Tandoor MCP Server tool call.

Start from Tandoor MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

Free to start. No card required.

13 Tandoor MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.