volcano.alerts.cap
Get Common Alerting Protocol (CAP) information for highly elevated volcanoes (ORANGE/WATCH or higher). CAP is the international emergency alert standard used by aviation authorities and civil protection agencies. Returns full CAP metadata: location (lat/lon/elevation), alert certainty, severity, ...
This record as markdown: /tools/io-github-whiteknightonhorse-apibase/volcano.alerts.cap.md
What volcano.alerts.cap does on Apibase
AI agents call volcano.alerts.cap 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 |
|---|---|---|---|
min_alert_level | string | — | Minimum alert level to include: ADVISORY, WATCH, or WARNING (default: all elevated) |
Parameters from the server's own tool schema.
Why volcano.alerts.cap is rated Low
Retrieves and queries public volcanic alert data with no side effects or modifications.
From the tool's definition Get Common Alerting Protocol information for volcanoes. Returns full CAP metadata. No auth.
Attacks that exploit this kind of access
The rule that runs volcano.alerts.cap 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.alerts.cap, this is the rule to start with:
volcano.alerts.cap 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.alerts.cap call is checked against it from then on.
Questions about volcano.alerts.cap
Get Common Alerting Protocol (CAP) information for highly elevated volcanoes (ORANGE/WATCH or higher). CAP is the international emergency alert standard used by aviation authorities and civil protection agencies. Returns full CAP metadata: location (lat/lon/elevation), alert certainty, severity, urgency, synopsis text, expiry time, and previous alert state. Only volcanoes that have been at ORANGE or above at least once appear here. Use for integration with emergency management systems, aviation NOTAM workflows, or real-time public alerting pipelines. No auth — USGS public domain. It is categorised as a Read tool in the Apibase MCP Server, which means it retrieves data without modifying state.
volcano.alerts.cap accepts 1 parameter: min_alert_level. 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.alerts.cap: 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.alerts.cap 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.alerts.cap 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.alerts.cap. 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.alerts.cap 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