volcano.status.monitored
Get all US volcanoes currently under active monitoring by the USGS Volcano Hazards Program. Returns ~69 volcanoes with current alert level (NORMAL/ADVISORY/WATCH/WARNING), aviation color code (GREEN/YELLOW/ORANGE/RED), observatory name, and the most recent notice URL. Monitoring requires ground-b...
This record as markdown: /tools/io-github-whiteknightonhorse-apibase/volcano.status.monitored.md
What volcano.status.monitored does on Apibase
AI agents call volcano.status.monitored 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 |
|---|---|---|---|
limit | integer | — | Maximum number of monitored volcanoes to return (1–200, default all ~69) |
Parameters from the server's own tool schema.
Why volcano.status.monitored is rated Low
Tool retrieves public USGS volcano monitoring data without modification, side effects, or sensitive operations.
From the tool's definition Get all US volcanoes currently under active monitoring by USGS. Returns alert levels, aviation codes, observatory names.
Attacks that exploit this kind of access
The rule that runs volcano.status.monitored 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.monitored, this is the rule to start with:
volcano.status.monitored 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.monitored call is checked against it from then on.
Questions about volcano.status.monitored
Get all US volcanoes currently under active monitoring by the USGS Volcano Hazards Program. Returns ~69 volcanoes with current alert level (NORMAL/ADVISORY/WATCH/WARNING), aviation color code (GREEN/YELLOW/ORANGE/RED), observatory name, and the most recent notice URL. Monitoring requires ground-based instruments to be operational — some volcanoes may be temporarily excluded during equipment outages. Use as a first step to identify volcano IDs for detail/notice lookups. No auth — USGS public domain, data updated in real time as notices are issued. It is categorised as a Read tool in the Apibase MCP Server, which means it retrieves data without modifying state.
volcano.status.monitored accepts 1 parameter: limit. 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.monitored: 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.monitored 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.monitored 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.monitored. 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.monitored 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