usda_nass_compare_crop_years

SERVERLivedatalink SOURCEhttps://livedatalink.ai/mcp

Low RISK CLASS

Category Read

Parameters 42 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/io-github-blackboxfoundry-livedatalink/usda-nass-compare-crop-years.md

WHAT IT DOES

What usda_nass_compare_crop_years does on Livedatalink

AI agents call usda_nass_compare_crop_years 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.
`years`	array	Yes	Two to seven distinct crop years.
`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.

RISK

Why usda_nass_compare_crop_years is rated Low

Even though usda_nass_compare_crop_years 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.

Risk signalsBulk/mass operation — affects multiple targets

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs usda_nass_compare_crop_years 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_compare_crop_years, this is the rule to start with:

usda_nass_compare_crop_years Allowed

usda_nass_compare_crop_years is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "usda_nass_compare_crop_years": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Livedatalink, apply this rule, and every usda_nass_compare_crop_years call is checked against it from then on.

FAQ

Questions about usda_nass_compare_crop_years

What does the usda_nass_compare_crop_years tool do? +

Compare 2–7 requested crop years across every hosted area, yield, and production metric for one USDA NASS crop/class. Returns each component value with its own unit and source release file, missing-year evidence, provenance, and caveats. Use this for 'compare 2019 and 2025 corn', '2020 vs 2025 soybean acres and yield', or 'compare winter wheat output across these years'. Final national annual summaries only. It is categorised as a Read tool in the Livedatalink MCP Server, which means it retrieves data without modifying state.

What parameters does usda_nass_compare_crop_years accept? +

usda_nass_compare_crop_years accepts 4 parameters: crop, years, crop_class, response_format. Required: crop, years. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on usda_nass_compare_crop_years? +

Register the Livedatalink MCP server in PolicyLayer and add a rule for usda_nass_compare_crop_years: 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.

What risk level is usda_nass_compare_crop_years? +

usda_nass_compare_crop_years is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit usda_nass_compare_crop_years? +

Yes. Add a rate_limit block to the usda_nass_compare_crop_years 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.

How do I block usda_nass_compare_crop_years completely? +

Set action: deny in the PolicyLayer policy for usda_nass_compare_crop_years. 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.

What MCP server provides usda_nass_compare_crop_years? +

usda_nass_compare_crop_years 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.

KEEP EXPLORING

More on Livedatalink, and thousands of servers like it.

This server

All 381 Livedatalink tools →

Across the catalogue

The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →