epa_facility_search
Search EPA-regulated facilities by state, city, zip, and/or facility name. Returns each facility's Registry ID (needed for the other EPA tools), address, and a snapshot of its compliance status across Clean Air Act, Clean Water Act, RCRA (waste), and Safe Drinking Water programs. Provide at least...
This record as markdown: /tools/io-github-blackboxfoundry-livedatalink/epa-facility-search.md
What epa_facility_search does on Livedatalink
AI agents call epa_facility_search 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 |
|---|---|---|---|
zip | string | — | 5-digit ZIP code (e.g. '20010'). |
city | string | — | City name (e.g. 'Washington'). |
name | string | — | Facility name or fragment (e.g. 'Pepco', 'refinery'). |
limit | number | — | Maximum facilities to return (default 25, max 100). |
state | string | — | Two-letter state or territory code (e.g. 'DC', 'TX', 'CA'). |
active_only | boolean | — | If true, only return facilities flagged with active enforcement/compliance activity. |
Parameters from the server's own tool schema.
Why epa_facility_search is rated Low
Even though epa_facility_search only reads data, uncontrolled read access leaks sensitive information and racks up API costs: an agent caught in a retry loop can make thousands of calls a minute without anyone noticing.
Attacks that exploit this kind of access
The rule that runs epa_facility_search 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_search, this is the rule to start with:
epa_facility_search 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_search call is checked against it from then on.
Questions about epa_facility_search
Search EPA-regulated facilities by state, city, zip, and/or facility name. Returns each facility's Registry ID (needed for the other EPA tools), address, and a snapshot of its compliance status across Clean Air Act, Clean Water Act, RCRA (waste), and Safe Drinking Water programs. Provide at least one filter; broad queries (e.g. state only for a large state) may be rejected as too broad, so add a city, zip, or name. It is categorised as a Read tool in the Livedatalink MCP Server, which means it retrieves data without modifying state.
epa_facility_search accepts 6 parameters: zip, city, name, limit, state, active_only. 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_search: 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_search 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_search 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_search. 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_search 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