AI agents call get_active_disasters to retrieve information from Api without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
eventTypes | string | null | — | Optional: semicolon-separated event types to filter (e.g., 'EQ;TC;FL') |
Parameters from the server's own tool schema.
This tool queries and retrieves existing disaster information from the GDACS system. It performs a read-only operation that returns data about active disasters grouped by type and geographic location. There is no indication of data modification, deletion, code execution, or financial impact.
From the tool's definition Tool name 'get_active_disasters' and description 'Get currently active disasters. Returns events with their geographic footprints grouped by disaster type' indicate a retrieval operation with no side effects.
Attacks that exploit this kind of access
Get currently active disasters. Returns events with their geographic footprints grouped by disaster type. It is categorised as a Read tool in the Api MCP Server, which means it retrieves data without modifying state.
get_active_disasters accepts 1 parameter: eventTypes. The full parameter table on this page comes from the server's own tool schema.
Register the Api MCP server in PolicyLayer and add a rule for get_active_disasters: 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 Api. Nothing to install.
get_active_disasters 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 get_active_disasters 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 get_active_disasters. 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.
get_active_disasters is provided by the Api MCP server (https://api.gdacs.org/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →