macrostrat.geology.map_units
Get the bedrock geologic map unit(s) at a specific point location (surface geology): formation/unit name, dominant lithology, description, age range, and recommended map color, sourced from compiled state/national geologic maps. Data: macrostrat.org/api/v2 /geologic_units/map, no auth required, C...
This record as markdown: /tools/io-github-whiteknightonhorse-apibase/macrostrat.geology.map-units.md
What macrostrat.geology.map_units does on Apibase
AI agents call macrostrat.geology.map_units 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 | Decimal degree latitude (WGS84) |
lng | number | Yes | Decimal degree longitude (WGS84) |
scale | string | — | Geologic map source scale (default returns the best-available match) |
Parameters from the server's own tool schema.
Why macrostrat.geology.map_units is rated Low
Queries geological data at coordinates; returns informational attributes without side effects or modifications.
From the tool's definition Get the bedrock geologic map unit(s) at a specific point location; retrieves formation name, lithology, description, age range
Attacks that exploit this kind of access
The rule that runs macrostrat.geology.map_units 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 macrostrat.geology.map_units, this is the rule to start with:
macrostrat.geology.map_units 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 macrostrat.geology.map_units call is checked against it from then on.
Questions about macrostrat.geology.map_units
Get the bedrock geologic map unit(s) at a specific point location (surface geology): formation/unit name, dominant lithology, description, age range, and recommended map color, sourced from compiled state/national geologic maps. Data: macrostrat.org/api/v2 /geologic_units/map, no auth required, CC BY 4.0. It is categorised as a Read tool in the Apibase MCP Server, which means it retrieves data without modifying state.
macrostrat.geology.map_units accepts 3 parameters: lat, lng, scale. Required: lat, lng. 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 macrostrat.geology.map_units: 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.
macrostrat.geology.map_units 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 macrostrat.geology.map_units 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 macrostrat.geology.map_units. 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.
macrostrat.geology.map_units 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