geodiva.geology.volcano_list
Browse Alaska's 356 volcanoes from the AVO GeoDIVA database, optionally filtered by NVEWS threat level, geologic age class, monitored-network status, or a name substring. Returns volcano ID, VNUM, name, type, composition, and threat rating for each match. Data: geodiva.avo.alaska.edu, no auth req...
This record as markdown: /tools/io-github-whiteknightonhorse-apibase/geodiva.geology.volcano-list.md
What geodiva.geology.volcano_list does on Apibase
AI agents call geodiva.geology.volcano_list 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_class | string | — | Filter by geologic age class — Historical/Holocene/Pleistocene, or Susp* (suspected) variants (client-side filter) |
threat_level | string | — | Filter by NVEWS eruption-hazard threat rating (client-side filter) |
name_contains | string | — | Case-insensitive substring match against volcano name or official name, e.g. "cleveland" |
monitored_only | boolean | — | If true, only return volcanoes actively monitored by AVO seismic/infrasound networks |
Parameters from the server's own tool schema.
Why geodiva.geology.volcano_list is rated Low
Tool queries publicly available geological data with filters; no side effects or data mutation.
From the tool's definition Browse, returns volcano data, public domain, no modifications
Attacks that exploit this kind of access
The rule that runs geodiva.geology.volcano_list 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.volcano_list, this is the rule to start with:
geodiva.geology.volcano_list 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.volcano_list call is checked against it from then on.
Questions about geodiva.geology.volcano_list
Browse Alaska's 356 volcanoes from the AVO GeoDIVA database, optionally filtered by NVEWS threat level, geologic age class, monitored-network status, or a name substring. Returns volcano ID, VNUM, name, type, composition, and threat rating for each match. 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.volcano_list accepts 4 parameters: age_class, threat_level, name_contains, monitored_only. 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.volcano_list: 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.volcano_list 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.volcano_list 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.volcano_list. 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.volcano_list 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