enviroatlas.communities.list
List or search the 32 US communities covered by EPA EnviroAtlas block-group ecosystem-service data (e.g. "Des Moines, IA", "Chicago, IL"). Returns community code, name, and census block group count for each. Call this first to find valid community codes/names for the other EnviroAtlas tools. Data...
This record as markdown: /tools/io-github-whiteknightonhorse-apibase/enviroatlas.communities.list.md
What enviroatlas.communities.list does on Apibase
AI agents call enviroatlas.communities.list 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 |
|---|---|---|---|
query | string | — | Filter the 32 EnviroAtlas pilot communities by name or state substring, case-insensitive (e.g. "TX" or "Portland"). Omit to list all of them. |
Parameters from the server's own tool schema.
Why enviroatlas.communities.list is rated Low
Retrieves public EPA community data without side effects or access control implications.
From the tool's definition List or search the 32 US communities
Attacks that exploit this kind of access
The rule that runs enviroatlas.communities.list 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 enviroatlas.communities.list, this is the rule to start with:
enviroatlas.communities.list 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 enviroatlas.communities.list call is checked against it from then on.
Questions about enviroatlas.communities.list
List or search the 32 US communities covered by EPA EnviroAtlas block-group ecosystem-service data (e.g. "Des Moines, IA", "Chicago, IL"). Returns community code, name, and census block group count for each. Call this first to find valid community codes/names for the other EnviroAtlas tools. Data: enviroatlas.epa.gov (US EPA), no auth required. It is categorised as a Read tool in the Apibase MCP Server, which means it retrieves data without modifying state.
enviroatlas.communities.list accepts 1 parameter: query. 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 enviroatlas.communities.list: 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.
enviroatlas.communities.list 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 enviroatlas.communities.list 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 enviroatlas.communities.list. 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.
enviroatlas.communities.list 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