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 use epa_water_or_air_violations to create or update resources in Livedatalink, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Livedatalink environment.
| 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 Medium
An AI agent can call epa_water_or_air_violations faster than any human can review: one bad instruction and it creates or modifies resources in Livedatalink by the hundred, each call as confident as the last.
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 stays usable, but capped: an agent stuck in a loop can't make hundreds of changes a minute. 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 Write tool in the Livedatalink MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
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 Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
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