macrostrat.geology.units_search
Get the rock units (formation/member/group names, top/bottom age in millions of years, thickness, lithology, and depositional environment) that make up a stratigraphic column, looked up by col_id (from macrostrat.columns_search) or by a lat/lng point. Data: macrostrat.org/api/v2, no auth required...
This record as markdown: /tools/io-github-whiteknightonhorse-apibase/macrostrat.geology.units-search.md
What macrostrat.geology.units_search does on Apibase
AI agents call macrostrat.geology.units_search 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 | — | Decimal degree latitude (WGS84) — must be supplied together with lng |
lng | number | — | Decimal degree longitude (WGS84) — must be supplied together with lat |
col_id | integer | — | Macrostrat column ID (from macrostrat.columns_search) to list rock units for |
Parameters from the server's own tool schema.
Why macrostrat.geology.units_search is rated Low
Tool queries geological data by ID or location, returning immutable formation records without modification or side effects.
From the tool's definition Get the rock units, looked up by col_id or lat/lng point. Data retrieval, no side effects.
Attacks that exploit this kind of access
The rule that runs macrostrat.geology.units_search 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.units_search, this is the rule to start with:
macrostrat.geology.units_search 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.units_search call is checked against it from then on.
Questions about macrostrat.geology.units_search
Get the rock units (formation/member/group names, top/bottom age in millions of years, thickness, lithology, and depositional environment) that make up a stratigraphic column, looked up by col_id (from macrostrat.columns_search) or by a lat/lng point. Data: macrostrat.org/api/v2, 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.units_search accepts 3 parameters: lat, lng, col_id. 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.units_search: 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.units_search 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.units_search 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.units_search. 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.units_search 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