epa_water_or_air_violations
Report a facility's air (Clean Air Act) or water (Clean Water Act / Safe Drinking Water Act) violations and the related compliance summaries. Set media to 'air', 'water', or 'all'. Requires an EPA Registry ID.
This record as markdown: /tools/io-github-blackboxfoundry-livedatalink/epa-water-or-air-violations.md
What epa_water_or_air_violations does on Livedatalink
AI agents call epa_water_or_air_violations to retrieve information from Livedatalink 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 |
|---|---|---|---|
media | string | — | Which media to report: 'air', 'water', or 'all' (default 'all'). |
registry_id | string | Yes | EPA Registry ID (FRS ID), the numeric facility identifier returned by epa_facility_search (e.g. '110001136271'). |
Parameters from the server's own tool schema.
Why epa_water_or_air_violations is rated Low
This tool fetches and returns compliance violation records from EPA databases. It is purely a read/query operation requiring an EPA Registry ID as input. No data is created, modified, or deleted. Low severity as it only retrieves publicly available regulatory information.
From the tool's definition 'Report a facility's air...or water...violations and the related compliance summaries' — retrieves/reports existing regulatory data
Attacks that exploit this kind of access
The rule that runs epa_water_or_air_violations safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Livedatalink, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For epa_water_or_air_violations, this is the rule to start with:
epa_water_or_air_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 Livedatalink, apply this rule, and every epa_water_or_air_violations call is checked against it from then on.
Questions about epa_water_or_air_violations
Report a facility's air (Clean Air Act) or water (Clean Water Act / Safe Drinking Water Act) violations and the related compliance summaries. Set media to 'air', 'water', or 'all'. Requires an EPA Registry ID. It is categorised as a Read tool in the Livedatalink MCP Server, which means it retrieves data without modifying state.
epa_water_or_air_violations accepts 2 parameters: media, registry_id. Required: registry_id. The full parameter table on this page comes from the server's own tool schema.
Register the Livedatalink MCP server in PolicyLayer and add a rule for epa_water_or_air_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 Livedatalink. Nothing to install.
epa_water_or_air_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 epa_water_or_air_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 epa_water_or_air_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.
epa_water_or_air_violations is provided by the Livedatalink MCP server (https://livedatalink.ai/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Livedatalink, and thousands of servers like it.
This server
Across the catalogue