Get all available data for a given commodity, location, and time.
AI agents call get_full_dataset to retrieve information from USDA NASS MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves or queries agricultural statistics data from USDA NASS without side effects. It fetches existing records based on parameters (commodity, location, time) but does not create, modify, delete, or execute operations. The sibling tools (get_db_record_count, get_param_values) further confirm this is a read-only data access pattern.
From the tool's definition Tool name 'get_full_dataset' and description 'Get all available data for a given commodity, location, and time' indicate data retrieval with no modification, deletion, or execution capabilities.
Attacks that exploit this kind of access
Get all available data for a given commodity, location, and time. It is categorised as a Read tool in the USDA NASS MCP Server MCP Server, which means it retrieves data without modifying state.
Register the USDA NASS MCP Server MCP server in PolicyLayer and add a rule for get_full_dataset: 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 USDA NASS MCP Server. Nothing to install.
get_full_dataset 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 get_full_dataset 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 get_full_dataset. 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.
get_full_dataset is provided by the USDA NASS MCP Server MCP server (kin5/nass-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →