nwis.streamflow.site_info
Get detailed metadata for a specific USGS hydrologic monitoring station: drainage area, HUC watershed code, precise coordinates, altitude, site type, state/county codes, and timezone. The drainage_area_sqmi field is critical for discharge-to-runoff calculations and flood frequency analysis. Compl...
This record as markdown: /tools/io-github-whiteknightonhorse-apibase/nwis.streamflow.site-info.md
What nwis.streamflow.site_info does on Apibase
AI agents call nwis.streamflow.site_info to retrieve information from Apibase 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 |
|---|---|---|---|
site_no | string | Yes | USGS gauge station number, 8–15 digits (e.g. "01646500" for Potomac River near DC, "09380000" for Colorado River at Lee Ferry). Use water.sites to search by sta |
Parameters from the server's own tool schema.
Why nwis.streamflow.site_info is rated Low
Tool retrieves publicly available hydrologic station metadata without modification, deletion, or execution capabilities.
From the tool's definition Get detailed metadata for a specific USGS hydrologic monitoring station; no auth, USGS public domain.
Attacks that exploit this kind of access
The rule that runs nwis.streamflow.site_info safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Apibase, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For nwis.streamflow.site_info, this is the rule to start with:
nwis.streamflow.site_info 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 Apibase, apply this rule, and every nwis.streamflow.site_info call is checked against it from then on.
Questions about nwis.streamflow.site_info
Get detailed metadata for a specific USGS hydrologic monitoring station: drainage area, HUC watershed code, precise coordinates, altitude, site type, state/county codes, and timezone. The drainage_area_sqmi field is critical for discharge-to-runoff calculations and flood frequency analysis. Complements water.sites (which searches by state/bounding box) by providing deep metadata for a known site. Use water.sites first to find the site_no, then call this for full station context. No auth — USGS public domain, unlimited calls. It is categorised as a Read tool in the Apibase MCP Server, which means it retrieves data without modifying state.
nwis.streamflow.site_info accepts 1 parameter: site_no. Required: site_no. The full parameter table on this page comes from the server's own tool schema.
Register the Apibase MCP server in PolicyLayer and add a rule for nwis.streamflow.site_info: 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 Apibase. Nothing to install.
nwis.streamflow.site_info 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 nwis.streamflow.site_info 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 nwis.streamflow.site_info. 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.
nwis.streamflow.site_info is provided by the Apibase MCP server (apibase-mcp-client). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Apibase, and thousands of servers like it.
This server
Across the catalogue