gdacs.disasters.details
Get detailed information for a specific GDACS disaster event by ID. Returns event name, alert level with justification, affected population at each severity level, coordinates, geometry for mapping, source agency, and situation report links.
This record as markdown: /tools/io-github-whiteknightonhorse-apibase/gdacs.disasters.details.md
What gdacs.disasters.details does on Apibase
AI agents call gdacs.disasters.details 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 |
|---|---|---|---|
event_id | integer | Yes | GDACS event ID (obtain via gdacs.alerts) |
event_type | string | Yes | Event type code: EQ=earthquake, TC=tropical cyclone, FL=flood, VO=volcano, DR=drought, TS=tsunami |
Parameters from the server's own tool schema.
Why gdacs.disasters.details is rated Low
Retrieves structured disaster event metadata with no side effects or data modification.
From the tool's definition Get detailed information for a specific GDACS disaster event by ID.
Attacks that exploit this kind of access
The rule that runs gdacs.disasters.details 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.details, this is the rule to start with:
gdacs.disasters.details 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.details call is checked against it from then on.
Questions about gdacs.disasters.details
Get detailed information for a specific GDACS disaster event by ID. Returns event name, alert level with justification, affected population at each severity level, coordinates, geometry for mapping, source agency, and situation report links. It is categorised as a Read tool in the Apibase MCP Server, which means it retrieves data without modifying state.
gdacs.disasters.details accepts 2 parameters: event_id, event_type. Required: event_id, event_type. 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.details: 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.details 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.details 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.details. 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.details 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