List EPA-regulated facilities in a US state (and optionally a city) from the EPA Facility Registry Service (FRS). Returns each facility once with all the EPA programs it is regulated under. Keyless.
AI agents call facilities_by_state to retrieve information from Mcp Epa Envirofacts without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
city | string | — | Optional city name, e.g. "Berkeley". |
limit | number | — | Max rows to fetch (default 20, max 50). |
state | string | Yes | 2-letter US state code, e.g. "CA". |
Parameters from the server's own tool schema.
This tool retrieves and queries publicly available EPA facility information filtered by state and optionally city. It performs no data creation, modification, deletion, code execution, or financial operations. The blast radius of misuse is minimal—an AI could retrieve facility lists but cannot harm systems or data. This is a straightforward Read operation.
From the tool's definition Tool description states it 'List[s] EPA-regulated facilities' and 'Returns each facility once with all the EPA programs it is regulated under.' The verb 'List' and the read-only nature of querying the EPA Facility Registry Service indicates data retrieval…
Attacks that exploit this kind of access
List EPA-regulated facilities in a US state (and optionally a city) from the EPA Facility Registry Service (FRS). Returns each facility once with all the EPA programs it is regulated under. Keyless. It is categorised as a Read tool in the Mcp Epa Envirofacts MCP Server, which means it retrieves data without modifying state.
facilities_by_state accepts 3 parameters: city, limit, state. Required: state. The full parameter table on this page comes from the server's own tool schema.
Register the Mcp Epa Envirofacts MCP server in PolicyLayer and add a rule for facilities_by_state: 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 Mcp Epa Envirofacts. Nothing to install.
facilities_by_state 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 facilities_by_state 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 facilities_by_state. 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.
facilities_by_state is provided by the Mcp Epa Envirofacts MCP server (pipeworx-io/mcp-epa-envirofacts). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →