get_nass_data
AI agents call get_nass_data to retrieve information from USDA MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The tool appears to retrieve NASS (National Agricultural Statistics Service) agricultural data based on naming convention and server purpose. No description is provided, but context indicates it queries a public agricultural database. This is a read-only data retrieval operation with no destructive, write, execute, or financial capabilities.
From the tool's definition Tool name 'get_nass_data' combined with server context indicating 'retrieval of historical crop statistics from NASS QuickStats' and pattern of sibling tools (get_ams_price, query_nass_flexible, search_ams_any) all suggesting data retrieval operations.
Attacks that exploit this kind of access
get_nass_data. It is categorised as a Read tool in the USDA MCP Server MCP Server, which means it retrieves data without modifying state.
Register the USDA MCP Server MCP server in PolicyLayer and add a rule for get_nass_data: 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 MCP Server. Nothing to install.
get_nass_data 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_nass_data 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_nass_data. 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_nass_data is provided by the USDA MCP Server MCP server (nstclore/usda-mcp). 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 →