water.usgs.sites
Search 1.5M+ USGS water monitoring sites by US state, county FIPS, bounding box, or site number. Returns site ID, station name, coordinates, altitude, HUC watershed code. Use site numbers with water.realtime for live data (USGS)
This record as markdown: /tools/io-github-whiteknightonhorse-apibase/water.usgs.sites.md
What water.usgs.sites does on Apibase
AI agents call water.usgs.sites 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 |
|---|---|---|---|
bbox | string | — | Bounding box: west,south,east,north in decimal degrees (e.g. "-105.5,39.5,-104.5,40.5") |
state | string | — | US state FIPS code, 2 chars (e.g. "CA", "NY", "CO") |
county | string | — | County FIPS code, 5 digits (e.g. "06037" for Los Angeles County) |
site_no | string | — | USGS site number (e.g. "09380000" for Colorado River at Lees Ferry) |
Parameters from the server's own tool schema.
Why water.usgs.sites is rated Low
Retrieves public water monitoring site metadata with no side effects or data modifications.
From the tool's definition Search USGS water monitoring sites. Returns site ID, station name, coordinates, altitude.
Attacks that exploit this kind of access
The rule that runs water.usgs.sites 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 water.usgs.sites, this is the rule to start with:
water.usgs.sites 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 water.usgs.sites call is checked against it from then on.
Questions about water.usgs.sites
Search 1.5M+ USGS water monitoring sites by US state, county FIPS, bounding box, or site number. Returns site ID, station name, coordinates, altitude, HUC watershed code. Use site numbers with water.realtime for live data (USGS). It is categorised as a Read tool in the Apibase MCP Server, which means it retrieves data without modifying state.
water.usgs.sites accepts 4 parameters: bbox, state, county, 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 water.usgs.sites: 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.
water.usgs.sites 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 water.usgs.sites 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 water.usgs.sites. 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.
water.usgs.sites 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