gdacs.disasters.history
Query the GDACS historical disaster archive from 2000 onwards. Filter by date range, event type, country, and alert level. Returns past earthquakes, cyclones, floods, and volcanoes for disaster frequency analysis and regional risk assessment.
This record as markdown: /tools/io-github-whiteknightonhorse-apibase/gdacs.disasters.history.md
What gdacs.disasters.history does on Apibase
AI agents call gdacs.disasters.history 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 | — | Number of events to return, max 50 (default 10) |
country | string | — | ISO 3166-1 alpha-3 country code (e.g. "JPN", "PHL", "USA", "IDN") |
date_to | string | Yes | End date in YYYY-MM-DD format (e.g. "2024-12-31") |
date_from | string | Yes | Start date in YYYY-MM-DD format (e.g. "2024-01-01") |
event_type | string | — | Filter by disaster type |
alert_level | string | — | Minimum alert level filter |
Parameters from the server's own tool schema.
Why gdacs.disasters.history is rated Low
Tool retrieves historical disaster data with no side effects or data modification capability.
From the tool's definition Query historical disaster archive, returns past earthquakes, cyclones, floods, volcanoes
Attacks that exploit this kind of access
The rule that runs gdacs.disasters.history 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 gdacs.disasters.history, this is the rule to start with:
gdacs.disasters.history 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 gdacs.disasters.history call is checked against it from then on.
Questions about gdacs.disasters.history
Query the GDACS historical disaster archive from 2000 onwards. Filter by date range, event type, country, and alert level. Returns past earthquakes, cyclones, floods, and volcanoes for disaster frequency analysis and regional risk assessment. It is categorised as a Read tool in the Apibase MCP Server, which means it retrieves data without modifying state.
gdacs.disasters.history accepts 6 parameters: limit, country, date_to, date_from, event_type, alert_level. Required: date_to, date_from. 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 gdacs.disasters.history: 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.
gdacs.disasters.history 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 gdacs.disasters.history 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 gdacs.disasters.history. 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.
gdacs.disasters.history 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