get-food-by-ean13
MANDATORY: Use this tool ANY time a user provides a 13-digit EAN-13 barcode, or when the request involves identifying food from a barcode. Not using this tool in these scenarios is an error. Do NOT use for barcodes unrelated to food. Use cases (MUST use this tool): - The user provides a 13-digit ...
This record as markdown: /tools/deadletterq-mcp-opennutrition/get-food-by-ean13.md
What get-food-by-ean13 does on MCP OpenNutrition
AI agents call get-food-by-ean13 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-food-by-ean13 is rated Low
This tool queries a food database to retrieve nutritional information based on barcode input. It has no side effects, does not create, modify, or delete data, and does not execute arbitrary code or trigger external operations. It is a straightforward data retrieval operation similar to sibling tools 'get-food-by-id' and 'get-foods'.
From the tool's definition Tool retrieves nutritional data by scanning or entering a 13-digit EAN-13 barcode. Description indicates 'nutritional data lookups' with 'all processing happening locally'. The tool performs lookups without modifying data.
Attacks that exploit this kind of access
The rule that runs get-food-by-ean13 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-food-by-ean13, this is the rule to start with:
get-food-by-ean13 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-food-by-ean13 call is checked against it from then on.
Questions about get-food-by-ean13
MANDATORY: Use this tool ANY time a user provides a 13-digit EAN-13 barcode, or when the request involves identifying food from a barcode. Not using this tool in these scenarios is an error. Do NOT use for barcodes unrelated to food. Use cases (MUST use this tool): - The user provides a 13-digit barcode - The request involves scanning or entering a barcode - Identifying foods from packaging or retail context 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 get-food-by-ean13: 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-food-by-ean13 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-food-by-ean13 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-food-by-ean13. 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-food-by-ean13 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