macrostrat.geology.columns_search
Search worldwide stratigraphic columns (a summary of the rock units at one location) by point location (lat/lng), stratigraphic name, chronostratigraphic time interval, lithology, or geologic age (Ma). Returns column IDs, names, coordinates, area, and thickness — use the returned col_id with macr...
This record as markdown: /tools/io-github-whiteknightonhorse-apibase/macrostrat.geology.columns-search.md
What macrostrat.geology.columns_search does on Apibase
AI agents call macrostrat.geology.columns_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 |
|---|---|---|---|
age | number | — | Numerical age in millions of years before present (Ma) |
lat | number | — | Decimal degree latitude (WGS84) — must be supplied together with lng |
lng | number | — | Decimal degree longitude (WGS84) — must be supplied together with lat |
lith | string | — | Lithology name to filter by, e.g. "sandstone" or "shale" |
age_top | number | — | Younger bound of an age range in Ma — must be used with age_bottom |
adjacents | boolean | — | If lat+lng given, also return columns touching the same polygon (default false) |
age_bottom | number | — | Older bound of an age range in Ma — must be used with age_top |
strat_name | string | — | Fuzzy stratigraphic name to match, e.g. "mancos" or "jordan" |
interval_name | string | — | Chronostratigraphic time interval name, e.g. "Permian" or "Cretaceous" |
Parameters from the server's own tool schema.
Why macrostrat.geology.columns_search is rated Low
Queries geological database with no side effects, no modifications or destructive operations.
From the tool's definition Search worldwide stratigraphic columns, returns column IDs, names, coordinates
Attacks that exploit this kind of access
The rule that runs macrostrat.geology.columns_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.columns_search, this is the rule to start with:
macrostrat.geology.columns_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.columns_search call is checked against it from then on.
Questions about macrostrat.geology.columns_search
Search worldwide stratigraphic columns (a summary of the rock units at one location) by point location (lat/lng), stratigraphic name, chronostratigraphic time interval, lithology, or geologic age (Ma). Returns column IDs, names, coordinates, area, and thickness — use the returned col_id with macrostrat.units_search or macrostrat.fossils_search. 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.columns_search accepts 9 parameters: age, lat, lng, lith, age_top, adjacents, age_bottom, strat_name, interval_name. 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.columns_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.columns_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.columns_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.columns_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.columns_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