New Your team’s decisions, in one playbook every coding agent works from. Never answer your agent twice

nwis.streamflow.basin_conditions

Get real-time streamflow readings for all active USGS gauge stations within a HUC-8 watershed basin. Returns current discharge (ft3/s) at every station in the basin — typically 5–40 sites — in a single call. Ideal for watershed-scale flood monitoring, drought assessment, and basin hydrology surve...

SERVERApibase SOURCEapibase-mcp-client
Low RISK CLASS
Category Read
Parameters 21 required
Recommended Allowedsee the rule below
Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/io-github-whiteknightonhorse-apibase/nwis.streamflow.basin-conditions.md

What nwis.streamflow.basin_conditions does on Apibase

AI agents call nwis.streamflow.basin_conditions 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.

ParameterTypeRequiredDescription
period string — ISO 8601 duration for how recent the data should be (e.g. "PT2H" = last 2 hours, "PT6H" = last 6 hours). Default is "PT2H". Longer periods return more data but
huc_code string Yes USGS Hydrologic Unit Code (HUC) — 8-digit watershed code (e.g. "02070008" for the Potomac Basin). Use 8-digit HUC for best results. Find HUC codes at water.usgs

Parameters from the server's own tool schema.

Why nwis.streamflow.basin_conditions is rated Low

Retrieves public USGS streamflow data with no side effects.

From the tool's definition Get real-time streamflow readings for all active USGS gauge stations

Questions about nwis.streamflow.basin_conditions

What does the nwis.streamflow.basin_conditions tool do? +

Get real-time streamflow readings for all active USGS gauge stations within a HUC-8 watershed basin. Returns current discharge (ft3/s) at every station in the basin — typically 5–40 sites — in a single call. Ideal for watershed-scale flood monitoring, drought assessment, and basin hydrology surveys. HUC-8 (8-digit Hydrologic Unit Code) defines a sub-basin level watershed (e.g. "02070008" = Potomac Basin). Find HUC codes at water.usgs.gov or use huc=XXXXXXXX for your area of interest. No auth — USGS public domain, updated every 15 minutes. It is categorised as a Read tool in the Apibase MCP Server, which means it retrieves data without modifying state.

What parameters does nwis.streamflow.basin_conditions accept? +

nwis.streamflow.basin_conditions accepts 2 parameters: period, huc_code. Required: huc_code. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on nwis.streamflow.basin_conditions? +

Register the Apibase MCP server in PolicyLayer and add a rule for nwis.streamflow.basin_conditions: 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.

What risk level is nwis.streamflow.basin_conditions? +

nwis.streamflow.basin_conditions is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit nwis.streamflow.basin_conditions? +

Yes. Add a rate_limit block to the nwis.streamflow.basin_conditions 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.

How do I block nwis.streamflow.basin_conditions completely? +

Set action: deny in the PolicyLayer policy for nwis.streamflow.basin_conditions. 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.

What MCP server provides nwis.streamflow.basin_conditions? +

nwis.streamflow.basin_conditions 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.

Across the catalogue

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of Apibase's. Pull the full record:

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.