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

Agent View of the PolicyLayer registry record for `get-food-by-ean13`. HTML page: https://policylayer.com/tools/deadletterq-mcp-opennutrition/get-food-by-ean13

## Facts

- Tool: `get-food-by-ean13`
- Server: MCP OpenNutrition (`deadletterq/mcp-opennutrition`) — https://policylayer.com/tools/deadletterq-mcp-opennutrition.md
- Homepage: https://github.com/deadletterq/mcp-opennutrition
- Risk category: Read (Low risk)
- Registry record: grade A, identity unverified
- Server rate-limited: no
- Parameters: 0
- Recommended policy verdict: Allowed

## Example call (MCP tools/call, JSON-RPC 2.0)

```json
{
  "jsonrpc": "2.0",
  "id": 1,
  "method": "tools/call",
  "params": {
    "name": "get-food-by-ean13",
    "arguments": {}
  }
}
```

## 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 own 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."

## Use case

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.

## Recommended policy (PolicyLayer)

Verdict: **Allowed**. Enforced by the PolicyLayer MCP gateway (https://policylayer.com/mcp-gateway) before a call reaches MCP OpenNutrition:

```json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "get-food-by-ean13": {}
  }
}
```

## Other tools on MCP OpenNutrition (3)

- `get-food-by-id` — Read — https://policylayer.com/tools/deadletterq-mcp-opennutrition/get-food-by-id.md
- `get-foods` — Read — https://policylayer.com/tools/deadletterq-mcp-opennutrition/get-foods.md
- `search-food-by-name` — Read — https://policylayer.com/tools/deadletterq-mcp-opennutrition/search-food-by-name.md

## For agents

This record is a snapshot. Live verdicts and the full registry:

- Check every server in your MCP config at once: `npx -y policylayer stack`
- Vet a server before you add it: install the mcp-precheck skill — `npx skills add https://policylayer.com` (skill text: https://policylayer.com/skill.md)
- Query the registry over MCP: endpoint `https://api.policylayer.com/mcp` — tools `check_mcp_server`, `check_mcp_stack`, `check_tool`, `search_registry`, `get_change_events`

---

Source: the PolicyLayer MCP registry — one continuously verified record per MCP server. Full record: https://policylayer.com/registry?q=deadletterq-mcp-opennutrition · API: https://policylayer.com/registry/api · Policy library: https://policylayer.com/policies/deadletterq-mcp-opennutrition