volcano.notices.latest
Get the text of the most recent official notice for a specific US volcano. USGS observatories issue daily updates, information statements, and activity alerts in a standardized format. Returns the notice as plain text (HTML stripped) and optionally the original HTML. Notices describe current volc...
This record as markdown: /tools/io-github-whiteknightonhorse-apibase/volcano.notices.latest.md
What volcano.notices.latest does on Apibase
AI agents call volcano.notices.latest 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 | Yes | USGS volcano code (e.g. ak277) or Smithsonian volcano number (e.g. 311090). Get IDs from volcano.us_catalog or volcano.monitored. |
Parameters from the server's own tool schema.
Why volcano.notices.latest is rated Low
Retrieves USGS volcanic notices without side effects; public domain data with no modification capabilities.
From the tool's definition Get the text of the most recent official notice for a specific US volcano. Returns the notice as plain text
Attacks that exploit this kind of access
The rule that runs volcano.notices.latest 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.notices.latest, this is the rule to start with:
volcano.notices.latest 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.notices.latest call is checked against it from then on.
Questions about volcano.notices.latest
Get the text of the most recent official notice for a specific US volcano. USGS observatories issue daily updates, information statements, and activity alerts in a standardized format. Returns the notice as plain text (HTML stripped) and optionally the original HTML. Notices describe current volcanic activity: seismicity, deformation, emissions, lava flow extent, ash cloud height, and recommended actions. Use with volcano_id from volcano.monitored or volcano.us_catalog. No auth — USGS public domain, data updated 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.notices.latest accepts 1 parameter: volcano_id. Required: 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 volcano.notices.latest: 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.notices.latest 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.notices.latest 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.notices.latest. 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.notices.latest 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