Get list of states from USGS Real-Time Flood Impacts API
AI agents call get_states 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 a static list of state identifiers from a public API. It performs no writes, deletions, code execution, or financial operations. The data returned is non-sensitive geographic metadata used for filtering or reference purposes. The blast radius of misuse is negligible—an AI agent calling this tool repeatedly would at worst cause minor API load, with no data loss or security breach.
From the tool's definition Tool name 'get_states' and description 'Get list of states' indicate a retrieval operation with no modification or side effects. This is a simple data query from the USGS Real-Time Flood Impacts API.
Attacks that exploit this kind of access
Get list of states 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_states: 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_states 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_states 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_states. 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_states 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 →