health.nutrition.food_search
Search 350K+ foods in the USDA FoodData Central database — nutrition facts, ingredients, branded products, and reference foods
This record as markdown: /tools/io-github-whiteknightonhorse-apibase/health.nutrition.food-search.md
What health.nutrition.food_search does on Apibase
AI agents call health.nutrition.food_search to retrieve information from Apibase without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
query | string | Yes | Food search query (e.g. "chicken breast", "brown rice", "vitamin D milk") |
data_type | string | — | USDA data type filter: "Foundation" (reference foods), "Branded" (brand-name products), "SR Legacy" (legacy reference), "all" (default) |
page_size | integer | — | Results per page (1-200, default 50) |
brand_owner | string | — | Filter by brand owner name (e.g. "General Mills", "Tyson") |
page_number | integer | — | Page number (default 1) |
Parameters from the server's own tool schema.
Why health.nutrition.food_search is rated Low
Queries a public nutrition database; retrieves information with no side effects or data modifications.
From the tool's definition Search 350K+ foods in the USDA FoodData Central database — nutrition facts, ingredients, branded products
Attacks that exploit this kind of access
The rule that runs health.nutrition.food_search safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Apibase, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For health.nutrition.food_search, this is the rule to start with:
health.nutrition.food_search 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 Apibase, apply this rule, and every health.nutrition.food_search call is checked against it from then on.
Questions about health.nutrition.food_search
Search 350K+ foods in the USDA FoodData Central database — nutrition facts, ingredients, branded products, and reference foods. It is categorised as a Read tool in the Apibase MCP Server, which means it retrieves data without modifying state.
health.nutrition.food_search accepts 5 parameters: query, data_type, page_size, brand_owner, page_number. Required: query. The full parameter table on this page comes from the server's own tool schema.
Register the Apibase MCP server in PolicyLayer and add a rule for health.nutrition.food_search: 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 Apibase. Nothing to install.
health.nutrition.food_search 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 health.nutrition.food_search 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 health.nutrition.food_search. 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.
health.nutrition.food_search is provided by the Apibase MCP server (apibase-mcp-client). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Apibase, and thousands of servers like it.
This server
Across the catalogue