echo.compliance.facility_detail
Retrieve detailed compliance profile for a specific EPA-regulated facility by Registry ID. Returns full address with county, coordinates, SIC/NAICS codes, HUC watershed code, federal facility status, facility creation/termination dates, and a complete list of environmental program interests (e.g....
This record as markdown: /tools/io-github-whiteknightonhorse-apibase/echo.compliance.facility-detail.md
What echo.compliance.facility_detail does on Apibase
AI agents call echo.compliance.facility_detail 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 for the facility (e.g. "110000350226"). Obtained from echo.facility_search results. |
Parameters from the server's own tool schema.
Why echo.compliance.facility_detail is rated Low
Tool queries EPA public compliance data without modification, deletion, or financial impact.
From the tool's definition Retrieve detailed compliance profile, Returns full address, coordinates, environmental program interests
Attacks that exploit this kind of access
The rule that runs echo.compliance.facility_detail 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.facility_detail, this is the rule to start with:
echo.compliance.facility_detail 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.facility_detail call is checked against it from then on.
Questions about echo.compliance.facility_detail
Retrieve detailed compliance profile for a specific EPA-regulated facility by Registry ID. Returns full address with county, coordinates, SIC/NAICS codes, HUC watershed code, federal facility status, facility creation/termination dates, and a complete list of environmental program interests (e.g. "CAA Stationary Source", "NPDES Permit"). Registry IDs are obtained from echo.compliance.facility_search results. Essential for due diligence, ESG screening, and permit verification. 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.facility_detail 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.facility_detail: 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.facility_detail 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.facility_detail 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.facility_detail. 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.facility_detail 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