search-food-by-name
MANDATORY: Use this tool ANY time you need to search for foods by name, synonym, or partial name. If a user provides a food name (common, brand, or alternate) or requests foods by name, you MUST use this tool. Not using this tool in these scenarios is an error. Do NOT use for non-food queries. Us...
This record as markdown: /tools/deadletterq-mcp-opennutrition/search-food-by-name.md
What search-food-by-name does on MCP OpenNutrition
AI agents call search-food-by-name to retrieve information from MCP OpenNutrition without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why search-food-by-name is rated Low
This tool performs a read-only search operation against a local food database. It retrieves and returns nutritional or food data without modifying, deleting, or executing anything. The blast radius of misuse is minimal—worst case, an AI agent returns irrelevant or duplicate food suggestions to a user. Low severity is appropriate for a simple data lookup with no destructive or financial consequences.
From the tool's definition Tool description states it "search[es] for foods by name" and retrieves data from a "comprehensive food database." Use cases describe "finding foods" and "suggesting food options," which are query/retrieval operations.
Attacks that exploit this kind of access
The rule that runs search-food-by-name safely
PolicyLayer is an MCP gateway: it sits between your AI agents and MCP OpenNutrition, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For search-food-by-name, this is the rule to start with:
search-food-by-name is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect MCP OpenNutrition, apply this rule, and every search-food-by-name call is checked against it from then on.
Questions about search-food-by-name
MANDATORY: Use this tool ANY time you need to search for foods by name, synonym, or partial name. If a user provides a food name (common, brand, or alternate) or requests foods by name, you MUST use this tool. Not using this tool in these scenarios is an error. Do NOT use for non-food queries. Use cases (MUST use this tool): - Users asking for foods by common, brand, or alternate names - Finding foods with partial or fuzzy name matches - Suggesting food options based on user input Examples: -. It is categorised as a Read tool in the MCP OpenNutrition MCP Server, which means it retrieves data without modifying state.
Register the MCP OpenNutrition MCP server in PolicyLayer and add a rule for search-food-by-name: 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 OpenNutrition. Nothing to install.
search-food-by-name 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 search-food-by-name 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 search-food-by-name. 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.
search-food-by-name is provided by the MCP OpenNutrition MCP server (deadletterq/mcp-opennutrition). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on MCP OpenNutrition, and thousands of servers like it.
This server
Across the catalogue