faostat.agriculture.food_loss
Retrieve the global food loss index and food loss percentage by food group (cereals, fruits & vegetables, meat, roots & tubers, pulses) for world regions. Data from FAO FAOSTAT — UN SDG Indicator 12.3.1. An index above 100 means more loss than the 2014-2016 baseline. Optionally filter by a specif...
This record as markdown: /tools/io-github-whiteknightonhorse-apibase/faostat.agriculture.food-loss.md
What faostat.agriculture.food_loss does on Apibase
AI agents call faostat.agriculture.food_loss 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 |
|---|---|---|---|
year | integer | — | Specific year to filter food loss data (e.g. 2022). Omit for full available range. |
end_year | integer | — | End year for the time series (default: latest available) |
start_year | integer | — | Start year for the time series (default: 2015, earliest available: 1961) |
Parameters from the server's own tool schema.
Why faostat.agriculture.food_loss is rated Low
Tool queries UN food loss statistics with no data modification or side effects.
From the tool's definition Retrieve global food loss index and percentage by food group
Attacks that exploit this kind of access
The rule that runs faostat.agriculture.food_loss 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 faostat.agriculture.food_loss, this is the rule to start with:
faostat.agriculture.food_loss 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 faostat.agriculture.food_loss call is checked against it from then on.
Questions about faostat.agriculture.food_loss
Retrieve the global food loss index and food loss percentage by food group (cereals, fruits & vegetables, meat, roots & tubers, pulses) for world regions. Data from FAO FAOSTAT — UN SDG Indicator 12.3.1. An index above 100 means more loss than the 2014-2016 baseline. Optionally filter by a specific year. It is categorised as a Read tool in the Apibase MCP Server, which means it retrieves data without modifying state.
faostat.agriculture.food_loss accepts 3 parameters: year, end_year, start_year. 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 faostat.agriculture.food_loss: 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.
faostat.agriculture.food_loss 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 faostat.agriculture.food_loss 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 faostat.agriculture.food_loss. 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.
faostat.agriculture.food_loss 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