epa_enforcement_search
List formal enforcement actions and penalties taken against a facility, plus a per-program summary of formal/informal actions, cases, and total penalties. Requires an EPA Registry ID (use epa_facility_search to find it).
This record as markdown: /tools/io-github-blackboxfoundry-livedatalink/epa-enforcement-search.md
What epa_enforcement_search does on Livedatalink
AI agents call epa_enforcement_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 |
|---|---|---|---|
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_enforcement_search is rated Low
This tool retrieves and queries publicly available EPA enforcement data about facilities. It has no side effects, does not modify or delete data, does not execute code or external operations, and does not involve financial transactions. It is a straightforward data lookup tool that returns information about regulatory actions already taken.
From the tool's definition Tool description states it 'List[s]' enforcement actions and penalties and provides a 'summary' — purely retrieval operations with no modification, deletion, or execution capability. The verb 'List' and 'summary' indicate read-only data access.
Attacks that exploit this kind of access
The rule that runs epa_enforcement_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_enforcement_search, this is the rule to start with:
epa_enforcement_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_enforcement_search call is checked against it from then on.
Questions about epa_enforcement_search
List formal enforcement actions and penalties taken against a facility, plus a per-program summary of formal/informal actions, cases, and total penalties. Requires an EPA Registry ID (use epa_facility_search to find it). It is categorised as a Read tool in the Livedatalink MCP Server, which means it retrieves data without modifying state.
epa_enforcement_search 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_enforcement_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_enforcement_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_enforcement_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_enforcement_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_enforcement_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