usda_nass_crop_history
Return bounded final annual USDA NASS national history for one major-crop metric from the self-hosted 2020–2026 annual-summary releases. Includes values, units, crop class, source release file, pagination, evidence hash, and attribution. Use this for 'US corn yield from 2019 to 2025', 'soybean pr...
This record as markdown: /tools/io-github-blackboxfoundry-livedatalink/usda-nass-crop-history.md
What usda_nass_crop_history does on Livedatalink
AI agents call usda_nass_crop_history to retrieve information from Livedatalink 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 |
|---|---|---|---|
crop | string | Yes | Crop name or supported alias: corn, soybeans, cotton, wheat, winter wheat, durum wheat, or spring wheat. |
limit | integer | — | Maximum crop years. Default 20. |
metric | string | Yes | Annual statistic to return. |
offset | integer | — | Crop years to skip. Default 0. |
end_year | integer | — | Four-digit crop year. Hosted snapshot coverage is 2019–2025. |
crop_class | string | — | Optional class. Required for bare 'wheat': winter, durum, or spring (excluding durum). |
start_year | integer | — | Four-digit crop year. Hosted snapshot coverage is 2019–2025. |
response_format | string | — | Human-readable markdown or machine-readable JSON. Default markdown. |
Parameters from the server's own tool schema.
Why usda_nass_crop_history is rated Low
Even though usda_nass_crop_history only reads data, uncontrolled read access leaks sensitive information and racks up API costs: an agent caught in a retry loop can make thousands of calls a minute without anyone noticing.
Attacks that exploit this kind of access
The rule that runs usda_nass_crop_history safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Livedatalink, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For usda_nass_crop_history, this is the rule to start with:
usda_nass_crop_history 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 Livedatalink, apply this rule, and every usda_nass_crop_history call is checked against it from then on.
Questions about usda_nass_crop_history
Return bounded final annual USDA NASS national history for one major-crop metric from the self-hosted 2020–2026 annual-summary releases. Includes values, units, crop class, source release file, pagination, evidence hash, and attribution. Use this for 'US corn yield from 2019 to 2025', 'soybean production history', or 'winter wheat acres harvested'. Available crop years are 2019–2025; this is not a forecast or state/county result. It is categorised as a Read tool in the Livedatalink MCP Server, which means it retrieves data without modifying state.
usda_nass_crop_history accepts 8 parameters: crop, limit, metric, offset, end_year, crop_class, start_year, response_format. Required: crop, metric. The full parameter table on this page comes from the server's own tool schema.
Register the Livedatalink MCP server in PolicyLayer and add a rule for usda_nass_crop_history: 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 Livedatalink. Nothing to install.
usda_nass_crop_history 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 usda_nass_crop_history 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 usda_nass_crop_history. 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.
usda_nass_crop_history is provided by the Livedatalink MCP server (https://livedatalink.ai/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Livedatalink, and thousands of servers like it.
This server
Across the catalogue