macrostrat.geology.fossils_search
Get Paleobiology Database (PBDB) fossil collections matched to a Macrostrat stratigraphic column or rock unit, looked up by col_id or unit_id (from macrostrat.columns_search / macrostrat.units_search), optionally narrowed by chronostratigraphic interval name. Returns collection names, ages, and P...
This record as markdown: /tools/io-github-whiteknightonhorse-apibase/macrostrat.geology.fossils-search.md
What macrostrat.geology.fossils_search does on Apibase
AI agents call macrostrat.geology.fossils_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 |
|---|---|---|---|
col_id | integer | — | Macrostrat column ID (from macrostrat.columns_search) to find fossil collections in |
unit_id | integer | — | Macrostrat unit ID (from macrostrat.units_search) to find fossil collections in |
interval_name | string | — | Optional chronostratigraphic interval name to further narrow results within col_id/unit_id |
Parameters from the server's own tool schema.
Why macrostrat.geology.fossils_search is rated Low
Tool queries and retrieves paleobiology data with no side effects or modifications.
From the tool's definition Get fossil collections matched to stratigraphic column, returns collection names, ages, occurrence counts.
Attacks that exploit this kind of access
The rule that runs macrostrat.geology.fossils_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.fossils_search, this is the rule to start with:
macrostrat.geology.fossils_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.fossils_search call is checked against it from then on.
Questions about macrostrat.geology.fossils_search
Get Paleobiology Database (PBDB) fossil collections matched to a Macrostrat stratigraphic column or rock unit, looked up by col_id or unit_id (from macrostrat.columns_search / macrostrat.units_search), optionally narrowed by chronostratigraphic interval name. Returns collection names, ages, and PBDB occurrence counts. 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.fossils_search accepts 3 parameters: col_id, unit_id, 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.fossils_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.fossils_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.fossils_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.fossils_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.fossils_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