epa_facility_compliance
Report a facility's current compliance status and recent non-compliance history by environmental program (Clean Air Act, Clean Water Act, RCRA hazardous waste, Safe Drinking Water Act). Shows quarters in non-compliance, quarters in significant non-compliance, and last inspection per statute. Requ...
This record as markdown: /tools/io-github-blackboxfoundry-livedatalink/epa-facility-compliance.md
What epa_facility_compliance does on Livedatalink
AI agents call epa_facility_compliance 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 |
|---|---|---|---|
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_facility_compliance is rated Low
This tool queries and retrieves historical compliance data from EPA records by facility ID. It has no side effects, does not modify state, and presents read-only access to public environmental regulatory information. The lowest severity applies because misuse would only result in information disclosure of already-public regulatory records.
From the tool's definition Tool description indicates it 'report[s] a facility's current compliance status and recent non-compliance history' — purely informational retrieval of public regulatory data.
Attacks that exploit this kind of access
The rule that runs epa_facility_compliance 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_facility_compliance, this is the rule to start with:
epa_facility_compliance 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_facility_compliance call is checked against it from then on.
Questions about epa_facility_compliance
Report a facility's current compliance status and recent non-compliance history by environmental program (Clean Air Act, Clean Water Act, RCRA hazardous waste, Safe Drinking Water Act). Shows quarters in non-compliance, quarters in significant non-compliance, and last inspection per statute. 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_facility_compliance accepts 1 parameter: 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_facility_compliance: 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_facility_compliance 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_facility_compliance 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_facility_compliance. 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_facility_compliance 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