enviroatlas.metrics.community_summary
Get aggregate EPA EnviroAtlas ecosystem-service statistics across all census block groups in an EnviroAtlas pilot community — average tree cover/impervious/green space percent, total population, total carbon stored and sequestration value, and average flood-risk population percent. Data: enviroat...
This record as markdown: /tools/io-github-whiteknightonhorse-apibase/enviroatlas.metrics.community-summary.md
What enviroatlas.metrics.community_summary does on Apibase
AI agents call enviroatlas.metrics.community_summary 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 |
|---|---|---|---|
community | string | Yes | EnviroAtlas pilot community code (e.g. "DMIA") or name (e.g. "Des Moines, IA"). Call enviroatlas.communities first to see all 32 covered communities. |
Parameters from the server's own tool schema.
Why enviroatlas.metrics.community_summary is rated Low
Retrieves public EPA environmental data without modifying, executing, or deleting anything.
From the tool's definition Get aggregate EPA EnviroAtlas ecosystem-service statistics across census block groups
Attacks that exploit this kind of access
The rule that runs enviroatlas.metrics.community_summary 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.metrics.community_summary, this is the rule to start with:
enviroatlas.metrics.community_summary 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.metrics.community_summary call is checked against it from then on.
Questions about enviroatlas.metrics.community_summary
Get aggregate EPA EnviroAtlas ecosystem-service statistics across all census block groups in an EnviroAtlas pilot community — average tree cover/impervious/green space percent, total population, total carbon stored and sequestration value, and average flood-risk population percent. 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.metrics.community_summary accepts 1 parameter: community. Required: community. 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.metrics.community_summary: 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.metrics.community_summary 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.metrics.community_summary 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.metrics.community_summary. 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.metrics.community_summary 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