usda_nass_crop_evidence_pack
Combine all hosted final annual USDA NASS national metrics for one major crop/class into a provenance-backed evidence pack with latest/as-of values, prior-year changes, and exact five-year comparisons. Use this for 'build a corn production evidence pack', 'summarize national soybean acreage yield...
This record as markdown: /tools/io-github-blackboxfoundry-livedatalink/usda-nass-crop-evidence-pack.md
What usda_nass_crop_evidence_pack does on Livedatalink
AI agents invoke usda_nass_crop_evidence_pack to trigger actions in Livedatalink. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call: builds kicked off, notifications sent, workflows started.
| Parameter | Type | Required | Description |
|---|---|---|---|
crop | string | Yes | Crop name or supported alias: corn, soybeans, cotton, wheat, winter wheat, durum wheat, or spring wheat. |
as_of_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). |
response_format | string | — | Human-readable markdown or machine-readable JSON. Default markdown. |
Parameters from the server's own tool schema.
Why usda_nass_crop_evidence_pack is rated High
usda_nass_crop_evidence_pack triggers real processes with real consequences. An agent gone sideways doesn't fire it once. It starts dozens of builds, sends mass notifications, or burns through compute before anyone looks up.
Attacks that exploit this kind of access
The rule that runs usda_nass_crop_evidence_pack 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_evidence_pack, this is the rule to start with:
usda_nass_crop_evidence_pack stays usable, but rate-capped: a runaway agent can't fire it dozens of times a minute. 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_evidence_pack call is checked against it from then on.
Questions about usda_nass_crop_evidence_pack
Combine all hosted final annual USDA NASS national metrics for one major crop/class into a provenance-backed evidence pack with latest/as-of values, prior-year changes, and exact five-year comparisons. Use this for 'build a corn production evidence pack', 'summarize national soybean acreage yield and output', or as an agriculture leg to combine with weather, freight, fuel, or futures data. Covers crop years 2019–2025 and is not a current forecast or trading recommendation. It is categorised as a Execute tool in the Livedatalink MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
usda_nass_crop_evidence_pack accepts 4 parameters: crop, as_of_year, crop_class, response_format. Required: crop. 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_evidence_pack: 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_evidence_pack is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the usda_nass_crop_evidence_pack 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_evidence_pack. 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_evidence_pack 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.
Across the catalogue