Get NWS/USGS crosswalk data from USGS Real-Time Flood Impacts API
AI agents call get_nws_usgs_crosswalk 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 queries and retrieves reference/mapping data (crosswalk data) between NWS and USGS systems. It has no side effects, does not modify or delete data, and does not execute commands or trigger external operations. The severity is low because access to reference/mapping data presents minimal risk to an AI agent.
From the tool's definition Tool retrieves 'crosswalk data' from USGS Real-Time Flood Impacts API; no modification, deletion, or execution capabilities described. All sibling tools are also read-only data retrieval operations (get_*, fetch_*).
Attacks that exploit this kind of access
Get NWS/USGS crosswalk data 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_nws_usgs_crosswalk: 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_nws_usgs_crosswalk 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_nws_usgs_crosswalk 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_nws_usgs_crosswalk. 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_nws_usgs_crosswalk 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 →