geodiva.geology.eruption_search
Search documented eruptions for an Alaska volcano by volcano_id (from geodiva.volcano_list), a specific eruption_id, or a start/end date range (years or ISO dates, including negative/BCE years for prehistoric eruptions). Returns eruption name, narrative description, and start/end date fields. Dat...
This record as markdown: /tools/io-github-whiteknightonhorse-apibase/geodiva.geology.eruption-search.md
What geodiva.geology.eruption_search does on Apibase
AI agents call geodiva.geology.eruption_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 |
|---|---|---|---|
edate_end | string | — | Eruption end-date range upper bound — must be paired with edate_start |
sdate_end | string | — | Eruption start-date range upper bound — must be paired with sdate_start, e.g. "2020-12-31" |
volcano_id | string | — | GeoDIVA volcano ID to list eruptions for, e.g. "ak52" (from geodiva.volcano_list) |
edate_start | string | — | Eruption end-date range lower bound — must be paired with edate_end |
eruption_id | integer | — | Specific eruption record ID to retrieve, e.g. 4111 |
sdate_start | string | — | Eruption start-date range lower bound — must be paired with sdate_end, e.g. "2000-01-01" |
Parameters from the server's own tool schema.
Why geodiva.geology.eruption_search is rated Low
Tool queries public geological eruption data without side effects or access restrictions.
From the tool's definition Search documented eruptions, returns eruption name, narrative description, start/end date fields.
Attacks that exploit this kind of access
The rule that runs geodiva.geology.eruption_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 geodiva.geology.eruption_search, this is the rule to start with:
geodiva.geology.eruption_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 geodiva.geology.eruption_search call is checked against it from then on.
Questions about geodiva.geology.eruption_search
Search documented eruptions for an Alaska volcano by volcano_id (from geodiva.volcano_list), a specific eruption_id, or a start/end date range (years or ISO dates, including negative/BCE years for prehistoric eruptions). Returns eruption name, narrative description, and start/end date fields. Data: geodiva.avo.alaska.edu, no auth required, US Government public domain. It is categorised as a Read tool in the Apibase MCP Server, which means it retrieves data without modifying state.
geodiva.geology.eruption_search accepts 6 parameters: edate_end, sdate_end, volcano_id, edate_start, eruption_id, sdate_start. 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 geodiva.geology.eruption_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.
geodiva.geology.eruption_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 geodiva.geology.eruption_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 geodiva.geology.eruption_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.
geodiva.geology.eruption_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