volcano.status.elevated
Get all US volcanoes currently in an elevated state (color code YELLOW, ORANGE, or RED; alert level ADVISORY, WATCH, or WARNING). Returns only volcanoes with active unrest or eruption. Includes volcano name, Smithsonian vnum, USGS volcano code, current alert level and color code, observatory, tim...
This record as markdown: /tools/io-github-whiteknightonhorse-apibase/volcano.status.elevated.md
What volcano.status.elevated does on Apibase
AI agents call volcano.status.elevated 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 |
|---|---|---|---|
color_code | string | — | Filter by aviation color code: YELLOW (advisory), ORANGE (watch), RED (warning) |
Parameters from the server's own tool schema.
Why volcano.status.elevated is rated Low
Tool retrieves real-time volcano status data from USGS without modifying any systems or data.
From the tool's definition Get all US volcanoes currently in elevated state, returns volcano data, no side effects.
Attacks that exploit this kind of access
The rule that runs volcano.status.elevated 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 volcano.status.elevated, this is the rule to start with:
volcano.status.elevated 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 volcano.status.elevated call is checked against it from then on.
Questions about volcano.status.elevated
Get all US volcanoes currently in an elevated state (color code YELLOW, ORANGE, or RED; alert level ADVISORY, WATCH, or WARNING). Returns only volcanoes with active unrest or eruption. Includes volcano name, Smithsonian vnum, USGS volcano code, current alert level and color code, observatory, time of last notice, and notice URL. Returns an empty array when all monitored volcanoes are at NORMAL/GREEN status. Ideal for real-time hazard monitoring dashboards and aviation safety agents. No auth — USGS public domain, updated within minutes of official notice issuance. It is categorised as a Read tool in the Apibase MCP Server, which means it retrieves data without modifying state.
volcano.status.elevated accepts 1 parameter: color_code. 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 volcano.status.elevated: 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.
volcano.status.elevated 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 volcano.status.elevated 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 volcano.status.elevated. 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.
volcano.status.elevated 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