sdwis.water.violations
Search EPA SDWIS for drinking water violations by state and violation type. Returns violation code, health-based flag (MCL/Treatment Technique), contaminant code, compliance status, measured value, compliance period, return-to-compliance date, and public notification tier. Filter by health_based=...
This record as markdown: /tools/io-github-whiteknightonhorse-apibase/sdwis.water.violations.md
What sdwis.water.violations does on Apibase
AI agents call sdwis.water.violations 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 | — | Maximum number of violations to return (1–100, default 20) |
state | string | — | State or primacy agency code (e.g. CA, TX). Two-letter abbreviation. Omit for all states. |
category | string | — | Violation category: MCL (Maximum Contaminant Level), TT (Treatment Technique), MRDL (Disinfectant), MR (Monitoring/Reporting), MON (Monitoring), RPT (Reporting) |
health_based | boolean | — | If true, return only health-based violations (MCL, TT, MRDL). If false or omitted, return all. |
Parameters from the server's own tool schema.
Why sdwis.water.violations is rated Low
Tool retrieves and queries public EPA water violation data with no side effects or modifications.
From the tool's definition Search EPA SDWIS for drinking water violations by state and violation type. Returns violation code, health-based flag, contaminant code, compliance status.
Attacks that exploit this kind of access
The rule that runs sdwis.water.violations 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 sdwis.water.violations, this is the rule to start with:
sdwis.water.violations 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 sdwis.water.violations call is checked against it from then on.
Questions about sdwis.water.violations
Search EPA SDWIS for drinking water violations by state and violation type. Returns violation code, health-based flag (MCL/Treatment Technique), contaminant code, compliance status, measured value, compliance period, return-to-compliance date, and public notification tier. Filter by health_based=true to focus on Maximum Contaminant Level (MCL) and Treatment Technique (TT) violations that directly endanger public health. Violation categories: MCL, TT, MRDL, MR, MON, RPT, PN. Use sdwis.water.enforcement to get enforcement actions associated with a PWSID from violations. 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.
sdwis.water.violations accepts 4 parameters: limit, state, category, health_based. 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 sdwis.water.violations: 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.
sdwis.water.violations 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 sdwis.water.violations 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 sdwis.water.violations. 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.
sdwis.water.violations 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