Get counties for a specific state from USGS Real-Time Flood Impacts API
AI agents call get_counties_by_state to retrieve information from USGS Water MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves reference data (counties) from the USGS API. It is purely informational and read-only, with no ability to modify, delete, or execute operations. The data returned is public geographic reference information. Severity is low due to negligible security impact if misused by an AI agent.
From the tool's definition Tool description states 'Get counties for a specific state' - a retrieval operation with no modification or destructive capability. The verb 'Get' indicates data querying. No side effects or state changes are possible.
Attacks that exploit this kind of access
Get counties for a specific state from USGS Real-Time Flood Impacts API. It is categorised as a Read tool in the USGS Water MCP MCP Server, which means it retrieves data without modifying state.
Register the USGS Water MCP server in PolicyLayer and add a rule for get_counties_by_state: 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 USGS Water MCP. Nothing to install.
get_counties_by_state 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_counties_by_state 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_counties_by_state. 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_counties_by_state is provided by the USGS Water MCP server (pgiffy/usgs-water-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 →