# 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

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

## Facts

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

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

## Use case

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.

## 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-foods": {}
  }
}
```

## Other tools on MCP OpenNutrition (3)

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