usgs_water_realtime
Real-time water data from USGS NWIS streamgages. Filter by site code, state, or parameter (e.g. '00060' = streamflow cfs, '00065' = gage height ft). Useful for flood-stage monitoring, drought tracking, and hydrological research.
This record as markdown: /tools/io-github-blackboxfoundry-livedatalink/usgs-water-realtime.md
What usgs_water_realtime does on Livedatalink
AI agents call usgs_water_realtime to retrieve information from Livedatalink without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
sites | string | — | Comma-separated USGS site codes (e.g. '01646500') |
state_cd | string | — | Two-letter state code; returns all active sites in the state |
parameter_cd | string | — | USGS parameter code (default '00060' streamflow). Common: 00060=streamflow, 00065=gage height, 00010=water temp, 00400=pH |
Parameters from the server's own tool schema.
Why usgs_water_realtime is rated Low
This tool queries a public USGS dataset and returns information. It has no side effects, does not modify data, execute code, delete records, or move money. It is a straightforward data retrieval tool suitable for monitoring and research purposes.
From the tool's definition Tool retrieves 'real-time water data' with filtering capabilities (site code, state, parameter). Descriptions of use cases (flood-stage monitoring, drought tracking, hydrological research) are all read-only queries with no mention of data modification,…
Attacks that exploit this kind of access
The rule that runs usgs_water_realtime safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Livedatalink, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For usgs_water_realtime, this is the rule to start with:
usgs_water_realtime is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Livedatalink, apply this rule, and every usgs_water_realtime call is checked against it from then on.
Questions about usgs_water_realtime
Real-time water data from USGS NWIS streamgages. Filter by site code, state, or parameter (e.g. '00060' = streamflow cfs, '00065' = gage height ft). Useful for flood-stage monitoring, drought tracking, and hydrological research. It is categorised as a Read tool in the Livedatalink MCP Server, which means it retrieves data without modifying state.
usgs_water_realtime accepts 3 parameters: sites, state_cd, parameter_cd. The full parameter table on this page comes from the server's own tool schema.
Register the Livedatalink MCP server in PolicyLayer and add a rule for usgs_water_realtime: 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 Livedatalink. Nothing to install.
usgs_water_realtime 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 usgs_water_realtime 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 usgs_water_realtime. 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.
usgs_water_realtime is provided by the Livedatalink MCP server (https://livedatalink.ai/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Livedatalink, and thousands of servers like it.
This server
Across the catalogue