epa.environment.toxic_releases
Search EPA Toxic Release Inventory (TRI) facilities by US state or ZIP code. Returns facility name, address, county, industry sector, and closed status. 600K+ regulated facilities. Source: EPA Envirofacts (US Gov open data).
This record as markdown: /tools/io-github-whiteknightonhorse-apibase/epa.environment.toxic-releases.md
What epa.environment.toxic_releases does on Apibase
AI agents call epa.environment.toxic_releases 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 |
|---|---|---|---|
limit | integer | — | Number of results (1-50, default 10) |
state | string | Yes | US state code (e.g. CA, TX, NY, FL) |
zip_code | string | — | ZIP code to filter (e.g. 90001). Overrides state filter if provided. |
Parameters from the server's own tool schema.
Why epa.environment.toxic_releases is rated Low
Tool queries public EPA environmental data without modifying records or triggering external operations.
From the tool's definition Search EPA Toxic Release Inventory facilities; returns facility name, address, county, industry sector
Attacks that exploit this kind of access
The rule that runs epa.environment.toxic_releases 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 epa.environment.toxic_releases, this is the rule to start with:
epa.environment.toxic_releases 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 epa.environment.toxic_releases call is checked against it from then on.
Questions about epa.environment.toxic_releases
Search EPA Toxic Release Inventory (TRI) facilities by US state or ZIP code. Returns facility name, address, county, industry sector, and closed status. 600K+ regulated facilities. Source: EPA Envirofacts (US Gov open data). It is categorised as a Read tool in the Apibase MCP Server, which means it retrieves data without modifying state.
epa.environment.toxic_releases accepts 3 parameters: limit, state, zip_code. Required: state. 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 epa.environment.toxic_releases: 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.
epa.environment.toxic_releases 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.environment.toxic_releases 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.environment.toxic_releases. 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.environment.toxic_releases 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