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

sdwis.water.service_areas

Look up the geographic service areas of EPA-regulated public water systems. Returns counties, cities, and zip codes served by each utility, along with area type and tribal codes. Filter by state or county to discover which water systems serve a specific area. Filter by PWSID to get all geographic...

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

This record as markdown: /tools/io-github-whiteknightonhorse-apibase/sdwis.water.service-areas.md

What sdwis.water.service_areas does on Apibase

AI agents call sdwis.water.service_areas 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
limit integer — Maximum number of service area records to return (1–100, default 20)
pwsid string — Public Water System Identifier (PWSID) to get service areas for a specific system (e.g. CA3310067)
state string — State or primacy agency code to filter service areas (e.g. CA, TX, FL)
county string — County name served by the water system (e.g. LOS ANGELES)

Parameters from the server's own tool schema.

Why sdwis.water.service_areas is rated Low

Retrieves EPA public water system service area data without side effects or data modification.

From the tool's definition Look up geographic service areas, returns counties, cities, zip codes. No modification or deletion.

Questions about sdwis.water.service_areas

What does the sdwis.water.service_areas tool do? +

Look up the geographic service areas of EPA-regulated public water systems. Returns counties, cities, and zip codes served by each utility, along with area type and tribal codes. Filter by state or county to discover which water systems serve a specific area. Filter by PWSID to get all geographic areas served by a specific utility. Useful for mapping water service boundaries, identifying utilities for an address, or understanding the geographic scope of a water quality issue. Data source: EPA SDWIS Federal Reporting Services Geographic Areas table, US Gov public domain. It is categorised as a Read tool in the Apibase MCP Server, which means it retrieves data without modifying state.

What parameters does sdwis.water.service_areas accept? +

sdwis.water.service_areas accepts 4 parameters: limit, pwsid, state, county. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on sdwis.water.service_areas? +

Register the Apibase MCP server in PolicyLayer and add a rule for sdwis.water.service_areas: 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 sdwis.water.service_areas? +

sdwis.water.service_areas is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit sdwis.water.service_areas? +

Yes. Add a rate_limit block to the sdwis.water.service_areas 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 sdwis.water.service_areas completely? +

Set action: deny in the PolicyLayer policy for sdwis.water.service_areas. 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 sdwis.water.service_areas? +

sdwis.water.service_areas 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.