waterpulse
WaterPulse: Global water intelligence API. 9 endpoints covering US groundwater (USGS), streamflow, drought (US Drought Monitor), water quality (EPA WQP), aquifer sustainability, flood risk, global water stress, a Coverage: Global Endpoints: • groundwater ($0.08): Groundwater levels (USGS) • strea...
This record as markdown: /tools/com-theaslangroupllc-pulse-pulsenetwork/waterpulse.md
What waterpulse does on Pulsenetwork
AI agents call waterpulse to retrieve information from Pulsenetwork 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 |
|---|---|---|---|
crop | string | — | Crop type — e.g. alfalfa, cotton, corn, almonds, rice |
lang | string | — | lang |
site | string | — | USGS site number — e.g. 09380000 (Colorado River at Lees Ferry) |
focus | string | — | agriculture | municipal | industrial | conflict | investment | all |
limit | string | — | Number of monitoring sites (5, 10, or 20) |
state | string | — | Two-letter US state code — e.g. CA, TX, AZ, FL, KS |
action | string | Yes | Which endpoint to call. Options: groundwater | streamflow | gauge | drought | quality | aquifer | flood-risk | global-stress | agriculture-use | supply-brief | |
region | string | — | Country, region, or river basin — e.g. India, Middle East, Nile Basin, Murray-Darling |
aquifer | string | — | Aquifer name — e.g. Ogallala, Central Valley, Floridan, Edwards, High Plains |
location | string | — | City, county, or river — e.g. Nashville TN, Mississippi River Iowa |
parameter | string | — | nitrates | phosphorus | ph | lead | arsenic | bacteria | pfas | turbidity |
Parameters from the server's own tool schema.
Why waterpulse is rated Low
Tool queries environmental and hydrological data with no mutation, deletion, or financial transaction capability beyond per-query billing.
From the tool's definition retrieves groundwater levels, streamflow, drought status, water quality, aquifer sustainability, flood risk data
Risk signalsHigh parameter count (11 properties)
Attacks that exploit this kind of access
The rule that runs waterpulse safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Pulsenetwork, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For waterpulse, this is the rule to start with:
waterpulse 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 Pulsenetwork, apply this rule, and every waterpulse call is checked against it from then on.
Questions about waterpulse
WaterPulse: Global water intelligence API. 9 endpoints covering US groundwater (USGS), streamflow, drought (US Drought Monitor), water quality (EPA WQP), aquifer sustainability, flood risk, global water stress, a Coverage: Global Endpoints: • groundwater ($0.08): Groundwater levels (USGS) • streamflow ($0.05): Streamflow — river discharge (USGS) • gauge ($0.01): River-gauge tick — deterministic USGS primitive • drought ($0.08): Drought status (US Drought Monitor) • quality ($0.08): Water quality (EPA WQP + USGS) • aquifer ($0.15): Aquifer sustainability analysis • flood-risk ($0.15): Flood risk intelligence • global-stress ($0.15): Global water stress by country/basin • agriculture-use ($0.15): Agricultural water use intelligence • supply-brief ($0.50): Municipal water supply brief • supply-snapshot ($0.25): Water supply numbers snapshot — deterministic preview. It is categorised as a Read tool in the Pulsenetwork MCP Server, which means it retrieves data without modifying state.
waterpulse accepts 11 parameters: crop, lang, site, focus, limit, state, action, region, aquifer, location, parameter. Required: action. The full parameter table on this page comes from the server's own tool schema.
Register the Pulsenetwork MCP server in PolicyLayer and add a rule for waterpulse: 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 Pulsenetwork. Nothing to install.
waterpulse 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 waterpulse 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 waterpulse. 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.
waterpulse is provided by the Pulsenetwork MCP server (https://pulse.theaslangroupllc.com/api/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Pulsenetwork, and thousands of servers like it.
This server
Across the catalogue