volcano.catalog.detail
Get detailed information for a single US volcano by its USGS volcano code or Smithsonian vnum. Returns name, coordinates, elevation, region, NVEWS threat rating, observatory, plain-text description (HTML stripped), official volcano page URL, image URL, and links to the HANS hazard page and newest...
This record as markdown: /tools/io-github-whiteknightonhorse-apibase/volcano.catalog.detail.md
What volcano.catalog.detail does on Apibase
AI agents call volcano.catalog.detail 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.catalog.detail is rated Low
Retrieves public USGS volcano data with no side effects or modifications.
From the tool's definition Get detailed information for a single US volcano, returns name, coordinates, elevation, region
Attacks that exploit this kind of access
The rule that runs volcano.catalog.detail 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.catalog.detail, this is the rule to start with:
volcano.catalog.detail 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.catalog.detail call is checked against it from then on.
Questions about volcano.catalog.detail
Get detailed information for a single US volcano by its USGS volcano code or Smithsonian vnum. Returns name, coordinates, elevation, region, NVEWS threat rating, observatory, plain-text description (HTML stripped), official volcano page URL, image URL, and links to the HANS hazard page and newest notice API. Use volcano.us_catalog or volcano.monitored to discover valid volcano IDs. Example: volcano_id="ak277" for Takawangha, "311120" for Great Sitkin. 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.catalog.detail 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.catalog.detail: 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.catalog.detail 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.catalog.detail 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.catalog.detail. 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.catalog.detail 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