geonet-nz.volcano.alert_level
Get the current Volcanic Alert Level and aviation colour code for New Zealand's 12 monitored volcanoes (e.g. Ruapehu, White Island/Whakaari, Taupo), including current activity summary and most-likely-hazards description. Optionally filter to a single volcano_id. Data: GeoNet (api.geonet.org.nz), ...
This record as markdown: /tools/io-github-whiteknightonhorse-apibase/geonet-nz.volcano.alert-level.md
What geonet-nz.volcano.alert_level does on Apibase
AI agents call geonet-nz.volcano.alert_level 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 |
|---|---|---|---|
volcano_id | string | — | Filter to a single volcano by ID (e.g. "ruapehu", "whiteisland"); returns all 12 New Zealand monitored volcanoes if omitted (client-side filter). |
Parameters from the server's own tool schema.
Why geonet-nz.volcano.alert_level is rated Low
Read-only query retrieving public volcano monitoring data with no side effects.
From the tool's definition Get the current Volcanic Alert Level... no auth required
Attacks that exploit this kind of access
The rule that runs geonet-nz.volcano.alert_level 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 geonet-nz.volcano.alert_level, this is the rule to start with:
geonet-nz.volcano.alert_level 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 geonet-nz.volcano.alert_level call is checked against it from then on.
Questions about geonet-nz.volcano.alert_level
Get the current Volcanic Alert Level and aviation colour code for New Zealand's 12 monitored volcanoes (e.g. Ruapehu, White Island/Whakaari, Taupo), including current activity summary and most-likely-hazards description. Optionally filter to a single volcano_id. Data: GeoNet (api.geonet.org.nz), run by GNS Science, no auth required. It is categorised as a Read tool in the Apibase MCP Server, which means it retrieves data without modifying state.
geonet-nz.volcano.alert_level accepts 1 parameter: volcano_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 geonet-nz.volcano.alert_level: 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.
geonet-nz.volcano.alert_level 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 geonet-nz.volcano.alert_level 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 geonet-nz.volcano.alert_level. 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.
geonet-nz.volcano.alert_level 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