enviroatlas.metrics.block_group
Get EPA EnviroAtlas ecosystem-service and environmental-health metrics for the census block group containing a lat/lon point — tree cover, green space, impervious area, air pollutant removal, carbon storage/sequestration, flood risk, heat reduction, and park/water-view access. Only covers the 32 ...
This record as markdown: /tools/io-github-whiteknightonhorse-apibase/enviroatlas.metrics.block-group.md
What enviroatlas.metrics.block_group does on Apibase
AI agents call enviroatlas.metrics.block_group 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 |
|---|---|---|---|
lat | number | Yes | Latitude in decimal degrees (e.g. 41.5868 for Des Moines, IA). |
lon | number | Yes | Longitude in decimal degrees (e.g. -93.6091 for Des Moines, IA). |
Parameters from the server's own tool schema.
Why enviroatlas.metrics.block_group is rated Low
Tool retrieves environmental and health metrics from EPA data without modifying, executing, or deleting anything.
From the tool's definition Get EPA EnviroAtlas metrics for census block group; returns data only
Attacks that exploit this kind of access
The rule that runs enviroatlas.metrics.block_group 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.block_group, this is the rule to start with:
enviroatlas.metrics.block_group 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.block_group call is checked against it from then on.
Questions about enviroatlas.metrics.block_group
Get EPA EnviroAtlas ecosystem-service and environmental-health metrics for the census block group containing a lat/lon point — tree cover, green space, impervious area, air pollutant removal, carbon storage/sequestration, flood risk, heat reduction, and park/water-view access. Only covers the 32 EPA pilot communities (see enviroatlas.communities); returns covered=false outside them. 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.block_group accepts 2 parameters: lat, lon. Required: lat, lon. 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.block_group: 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.block_group 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.block_group 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.block_group. 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.block_group 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