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

sdwis.water.enforcement

Look up EPA enforcement actions taken against public water systems under the Safe Drinking Water Act. Filter by PWSID (Public Water System Identifier) to get all enforcement history for a specific utility, or filter by enforcement action type code. Returns enforcement date, action type, and origi...

SERVERApibase SOURCEapibase-mcp-client
Low RISK CLASS
Category Read
Parameters 30 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.enforcement.md

What sdwis.water.enforcement does on Apibase

AI agents call sdwis.water.enforcement 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 enforcement actions to return (1–100, default 20)
pwsid string — Public Water System Identifier (PWSID) to look up enforcement actions for a specific system (e.g. CA3310067)
action_type string — Enforcement action type code (e.g. EFG for Formal Enforcement Order, 3EF for Third Violation)

Parameters from the server's own tool schema.

Why sdwis.water.enforcement is rated Low

Retrieves public EPA enforcement data without side effects or modification capability.

From the tool's definition Look up EPA enforcement actions; returns enforcement date, action type, originator.

Risk signalsAdmin/system-level operation

Questions about sdwis.water.enforcement

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

Look up EPA enforcement actions taken against public water systems under the Safe Drinking Water Act. Filter by PWSID (Public Water System Identifier) to get all enforcement history for a specific utility, or filter by enforcement action type code. Returns enforcement date, action type, and originator. Enforcement types include Formal Administrative Orders (EFG), Compliance Schedules, Referral to State, and Civil Penalties. Combine with sdwis.water.violations to understand the full compliance picture for a water system. Data source: EPA SDWIS Federal Reporting Services, 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.enforcement accept? +

sdwis.water.enforcement accepts 3 parameters: limit, pwsid, action_type. The full parameter table on this page comes from the server's own tool schema.

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

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

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

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

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

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

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