gdacs.disasters.alerts
Get current and recent global disaster alerts from the UN GDACS system. Returns earthquakes, tropical cyclones, floods, volcanoes, droughts, and tsunamis with color-coded severity (Green/Orange/Red), affected country, coordinates, and population impact estimates.
This record as markdown: /tools/io-github-whiteknightonhorse-apibase/gdacs.disasters.alerts.md
What gdacs.disasters.alerts does on Apibase
AI agents call gdacs.disasters.alerts 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) |
event_type | string | — | Filter by disaster type: EQ=earthquake, TC=tropical cyclone, FL=flood, VO=volcano, DR=drought, TS=tsunami |
alert_level | string | — | Minimum alert level filter: Green (low), Orange (medium), Red (high impact) |
Parameters from the server's own tool schema.
Why gdacs.disasters.alerts is rated Low
Retrieves and queries disaster alert data from UN GDACS system without modifying or triggering external operations.
From the tool's definition Get current and recent global disaster alerts, queries data, no side effects
Attacks that exploit this kind of access
The rule that runs gdacs.disasters.alerts 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.alerts, this is the rule to start with:
gdacs.disasters.alerts 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.alerts call is checked against it from then on.
Questions about gdacs.disasters.alerts
Get current and recent global disaster alerts from the UN GDACS system. Returns earthquakes, tropical cyclones, floods, volcanoes, droughts, and tsunamis with color-coded severity (Green/Orange/Red), affected country, coordinates, and population impact estimates. It is categorised as a Read tool in the Apibase MCP Server, which means it retrieves data without modifying state.
gdacs.disasters.alerts accepts 3 parameters: limit, event_type, 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 gdacs.disasters.alerts: 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.alerts 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.alerts 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.alerts. 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.alerts 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