Low Risk

get_recipes

Search for recipes in Tandoor based on various criteria.

How to control get_recipes ↓

What get_recipes does on Tandoor MCP Server

AI agents call get_recipes 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_recipes needs a policy

This tool retrieves recipe data from the Tandoor system without modifying, deleting, or executing any operations. It is a straightforward read operation that queries existing recipes. The severity is low because misuse would only expose recipe information that users likely intend to be accessible, with no capability to alter system state or cause harm.

From the tool's definition Tool name 'get_recipes' and description 'Search for recipes in Tandoor based on various criteria' indicate a query/retrieval operation with no side effects.

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

How to control get_recipes

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_recipes:

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

get_recipes 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_recipes

What does the get_recipes tool do? +

Search for recipes in Tandoor based on various criteria. 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_recipes? +

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

What risk level is get_recipes? +

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

Can I rate-limit get_recipes? +

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.

How do I block get_recipes completely? +

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.

What MCP server provides get_recipes? +

get_recipes 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.