get_foods

THE RISK

Low Risk

Why get_foods needs a policy

This is a straightforward data retrieval tool that queries foods in the Tandoor recipe system. It performs a search/list operation without side effects, matching the Read category. The severity is low because accessing food data poses minimal risk—it is informational only, with no ability to modify systems, execute commands, or cause financial harm.

From the tool's definition Tool name 'get_foods' and description 'List or search for foods' indicate a retrieval operation with no modification, deletion, or execution of external commands.

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

POLICY

How to control get_foods

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

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "get_foods": {}
  }
}

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

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

CAP THIS TOOL →

Free to start. No card required.

EXPLORE

Related tools and policies

More Tandoor MCP Server tools

Destructive remove_shopping_list_item Remove an item from the shopping list. Write add_shopping_list_item Add an item to the shopping list, allowing food/unit names or IDs. Write create_tandoor_meal_plan Add one or more recipes to the Tandoor meal plan for a specific date and meal type. Write create_tandoor_recipe Create a new recipe in Tandoor. Write update_shopping_list_item Update an existing shopping list item (e.g., check/uncheck, change amount). Read get_keywords List or search for keywords. Read get_meal_plans Retrieve meal plan entries from Tandoor, optionally filtering by date range and meal type. Read get_meal_types List all available meal types in Tandoor.

All 13 Tandoor MCP Server tools →

Read tools on other servers

M-Team MCP Server get_torrent_detail YouTube MCP Server search_channel Android Forensics ADB MCP Server parse_browser_history 0xarchive web3_challenge

Go deeper

The MCP Attack Database → Documented attack patterns against MCP deployments — and the policies that stop them.
Data exfiltration → How read access becomes an exfiltration channel when chained with untrusted content.
MCP token cost → What connecting this server costs in context-window tokens on every request.
Rate Limiting MCP Tool Calls: A Practical Guide →
MCP Security: Why Prompt Guardrails Aren't Enough →

FAQ

Questions about get_foods

What does the get_foods tool do? +

List or search for foods. 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_foods? +

Register the Tandoor MCP Server MCP server in PolicyLayer and add a rule for get_foods: 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_foods? +

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

Can I rate-limit get_foods? +

Yes. Add a rate_limit block to the get_foods 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_foods completely? +

Set action: deny in the PolicyLayer policy for get_foods. 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_foods? +

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

CHECK YOUR STACK →