get_db_record_count
AI agents call get_db_record_count 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 a count of records from a database, which is a read-only operation with no side effects. It does not modify, delete, or execute arbitrary code. The blast radius of misuse is minimal—returning an incorrect count has no impact on data integrity or availability. The empty description lowers confidence slightly, but the tool name and context are sufficiently clear.
From the tool's definition Tool name 'get_db_record_count' indicates retrieval of metadata (record count). No parameters or description provided, but the function name and sibling tools (get_full_dataset, get_param_values) on a USDA NASS statistics data server confirm this is a…
Attacks that exploit this kind of access
get_db_record_count. 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_db_record_count: 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_db_record_count 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_db_record_count 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_db_record_count. 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_db_record_count 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 →