echo.compliance.violations
Retrieve enforcement actions and violation history for a specific EPA-regulated facility. Returns enforcement activity type, action type, settlement date, federal and state penalties assessed, supplemental environmental project (SEP) amounts, and affected program codes (e.g. CAA, CWA, RCRA). Regi...
This record as markdown: /tools/io-github-whiteknightonhorse-apibase/echo.compliance.violations.md
What echo.compliance.violations does on Apibase
AI agents call echo.compliance.violations to retrieve information from Apibase 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 Facility Registry System (FRS) Registry ID to retrieve enforcement and violation history for (e.g. "110000350226"). Obtained from echo.facility_search resul |
Parameters from the server's own tool schema.
Why echo.compliance.violations is rated Low
Tool retrieves historical compliance data from public EPA registry without modifying records or triggering external actions.
From the tool's definition Retrieve enforcement actions and violation history; Returns enforcement activity, penalties, affected program codes.
Attacks that exploit this kind of access
The rule that runs echo.compliance.violations safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Apibase, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For echo.compliance.violations, this is the rule to start with:
echo.compliance.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 Apibase, apply this rule, and every echo.compliance.violations call is checked against it from then on.
Questions about echo.compliance.violations
Retrieve enforcement actions and violation history for a specific EPA-regulated facility. Returns enforcement activity type, action type, settlement date, federal and state penalties assessed, supplemental environmental project (SEP) amounts, and affected program codes (e.g. CAA, CWA, RCRA). Registry IDs are obtained from echo.compliance.facility_search results. Critical for environmental liability assessment, ESG due diligence, and compliance monitoring. Source: EPA ECHO — US Gov public domain, no auth required. It is categorised as a Read tool in the Apibase MCP Server, which means it retrieves data without modifying state.
echo.compliance.violations 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 Apibase MCP server in PolicyLayer and add a rule for echo.compliance.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 Apibase. Nothing to install.
echo.compliance.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 echo.compliance.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 echo.compliance.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.
echo.compliance.violations is provided by the Apibase MCP server (apibase-mcp-client). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Apibase, and thousands of servers like it.
This server
Across the catalogue