get-foods
MANDATORY: Use this tool ANY time a user requests an overview, wants to browse foods, or asks for a list of foods (by type, category, or general request). Not using this tool in these scenarios is an error. Do NOT use for non-food or non-list queries. Use cases (MUST use this tool): - Displaying ...
This record as markdown: /tools/deadletterq-mcp-opennutrition/get-foods.md
What get-foods does on MCP OpenNutrition
AI agents call get-foods 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 get-foods is rated Low
This is a straightforward read-only query tool that retrieves and displays food items from a local nutrition database. The operation has no side effects, cannot modify data, and presents minimal risk even if misused—worst case, an AI agent returns irrelevant food listings.
From the tool's definition Tool name 'get-foods' and description indicate it retrieves or lists food data from a database: 'Displaying lists for selection or browsing', 'Providing overviews of available foods', 'search-food-by-name'.
Attacks that exploit this kind of access
The rule that runs get-foods 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 get-foods, this is the rule to start with:
get-foods 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 get-foods call is checked against it from then on.
Questions about get-foods
MANDATORY: Use this tool ANY time a user requests an overview, wants to browse foods, or asks for a list of foods (by type, category, or general request). Not using this tool in these scenarios is an error. Do NOT use for non-food or non-list queries. Use cases (MUST use this tool): - Displaying lists for selection or browsing - Providing overviews of available foods - Supporting queries like. 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 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 MCP OpenNutrition. Nothing to install.
get-foods 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-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.
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.
get-foods 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