New Your team’s decisions, in one playbook every coding agent works from. Never answer your agent twice

echo.compliance.air_facilities

Search facilities regulated under the Clean Air Act (CAA) by ZIP code or facility name. Returns facility name, address, coordinates, CAA permit types and status, quarters of noncompliance, inspection count, and High Priority Violation (HPV) flag. Ideal for air quality compliance monitoring, permi...

SERVERApibase SOURCEapibase-mcp-client
Low RISK CLASS
Category Read
Parameters 40 required
Recommended Allowedsee the rule below
Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/io-github-whiteknightonhorse-apibase/echo.compliance.air-facilities.md

What echo.compliance.air_facilities does on Apibase

AI agents call echo.compliance.air_facilities 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.

ParameterTypeRequiredDescription
limit integer — Maximum number of facilities to return (1–50). Default 10.
state string — Two-letter US state code to narrow results (e.g. "TX", "OH"). Required when using facility_name without zip_code.
zip_code string — US ZIP code to search within (e.g. "77002"). Recommended for precise results. Provide either zip_code or facility_name.
facility_name string — Partial or full facility name to search for (e.g. "Exxon"). Use with state for best results.

Parameters from the server's own tool schema.

Why echo.compliance.air_facilities is rated Low

Tool queries public EPA compliance data without modifying or executing operations; pure information retrieval.

From the tool's definition Search facilities, Returns facility name, address, coordinates, CAA permit types and status

Questions about echo.compliance.air_facilities

What does the echo.compliance.air_facilities tool do? +

Search facilities regulated under the Clean Air Act (CAA) by ZIP code or facility name. Returns facility name, address, coordinates, CAA permit types and status, quarters of noncompliance, inspection count, and High Priority Violation (HPV) flag. Ideal for air quality compliance monitoring, permit research, and environmental due diligence. Use zip_code for location search or facility_name with state for targeted search. Source: EPA ECHO Air program data — 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.

What parameters does echo.compliance.air_facilities accept? +

echo.compliance.air_facilities accepts 4 parameters: limit, state, zip_code, facility_name. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on echo.compliance.air_facilities? +

Register the Apibase MCP server in PolicyLayer and add a rule for echo.compliance.air_facilities: 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.

What risk level is echo.compliance.air_facilities? +

echo.compliance.air_facilities is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit echo.compliance.air_facilities? +

Yes. Add a rate_limit block to the echo.compliance.air_facilities 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.

How do I block echo.compliance.air_facilities completely? +

Set action: deny in the PolicyLayer policy for echo.compliance.air_facilities. 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.

What MCP server provides echo.compliance.air_facilities? +

echo.compliance.air_facilities 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.

Across the catalogue

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of Apibase's. Pull the full record:

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.