epa.environment.water_systems
Search public water systems by US state. Returns system name, PWSID, activity status, primacy agency, EPA region, population served, and service connections. Source: EPA Safe Drinking Water Act data.
This record as markdown: /tools/io-github-whiteknightonhorse-apibase/epa.environment.water-systems.md
What epa.environment.water_systems does on Apibase
AI agents call epa.environment.water_systems 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 |
|---|---|---|---|
limit | integer | — | Number of results (1-50, default 10) |
state | string | Yes | US state code (e.g. FL, CA, TX) |
Parameters from the server's own tool schema.
Why epa.environment.water_systems is rated Low
Tool queries public EPA database and returns informational data with no side effects.
From the tool's definition Search public water systems, returns system name, PWSID, activity status, EPA region.
Attacks that exploit this kind of access
The rule that runs epa.environment.water_systems 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 epa.environment.water_systems, this is the rule to start with:
epa.environment.water_systems 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 epa.environment.water_systems call is checked against it from then on.
Questions about epa.environment.water_systems
Search public water systems by US state. Returns system name, PWSID, activity status, primacy agency, EPA region, population served, and service connections. Source: EPA Safe Drinking Water Act data. It is categorised as a Read tool in the Apibase MCP Server, which means it retrieves data without modifying state.
epa.environment.water_systems accepts 2 parameters: limit, state. Required: state. 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 epa.environment.water_systems: 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.
epa.environment.water_systems 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 epa.environment.water_systems 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 epa.environment.water_systems. 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.
epa.environment.water_systems 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