nutrition.fatsecret.search
Search 2.3M+ food items by name — branded products, restaurant meals, generic foods from 190+ countries. Returns food ID, name, type, brand, and per-serving summary (calories, fat, carbs, protein). Use food_id for detailed nutritional lookup (FatSecret)
This record as markdown: /tools/io-github-whiteknightonhorse-apibase/nutrition.fatsecret.search.md
What nutrition.fatsecret.search does on Apibase
AI agents call nutrition.fatsecret.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 |
|---|---|---|---|
page | integer | — | Page number for pagination (default 0) |
query | string | Yes | Food name to search (e.g. "chicken breast", "banana", "greek yogurt") |
max_results | integer | — | Results per page (default 20, max 50) |
Parameters from the server's own tool schema.
Why nutrition.fatsecret.search is rated Low
Tool retrieves food database information without side effects or external modifications.
From the tool's definition Search 2.3M+ food items by name — returns food ID, name, type, brand, summary
Attacks that exploit this kind of access
The rule that runs nutrition.fatsecret.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 nutrition.fatsecret.search, this is the rule to start with:
nutrition.fatsecret.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 nutrition.fatsecret.search call is checked against it from then on.
Questions about nutrition.fatsecret.search
Search 2.3M+ food items by name — branded products, restaurant meals, generic foods from 190+ countries. Returns food ID, name, type, brand, and per-serving summary (calories, fat, carbs, protein). Use food_id for detailed nutritional lookup (FatSecret). It is categorised as a Read tool in the Apibase MCP Server, which means it retrieves data without modifying state.
nutrition.fatsecret.search accepts 3 parameters: page, query, max_results. 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 nutrition.fatsecret.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.
nutrition.fatsecret.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 nutrition.fatsecret.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 nutrition.fatsecret.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.
nutrition.fatsecret.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