# get-food-by-id

MANDATORY: Use this tool ANY time a user provides a food ID (e.g., fd_xxx), or when you have a food ID from a previous step and need detailed information. Not using this tool in these scenarios is an error. Do NOT use for non-food IDs or unrelated queries. Use cases (MUST use this tool): - The user provides a food ID - A previous step yielded a food ID - The user requests nutrition, ingredients, or labeling for a specific product Example: -

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

## Facts

- Tool: `get-food-by-id`
- 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-id",
    "arguments": {}
  }
}
```

## Why get-food-by-id is rated Low

This is a straightforward data retrieval operation against a food database. It queries and returns nutritional data, ingredients, and labeling information based on a provided food ID. No data is created, modified, deleted, or executed. The local processing mentioned refers to the query execution environment, not arbitrary code execution.

From the tool's own definition: "Tool retrieves detailed food information by ID (nutrition, ingredients, labeling) with no side effects. Name contains 'get-' prefix and description emphasizes data lookup without modification, deletion, or execution."

## Use case

AI agents call get-food-by-id 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-id": {}
  }
}
```

## Other tools on MCP OpenNutrition (3)

- `get-food-by-ean13` — Read — https://policylayer.com/tools/deadletterq-mcp-opennutrition/get-food-by-ean13.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