AI agents call get_disaster_statistics 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 |
|---|---|---|---|
toDate | string | null | — | End date for statistics period |
country | string | null | — | Country filter |
fromDate | string | null | — | Start date for statistics period |
alertLevel | string | null | — | Alert level filter |
eventTypes | string | null | — | Comma-separated event types to include |
Parameters from the server's own tool schema.
This tool retrieves and aggregates historical disaster statistics for analysis. It performs no side effects, creates no new data, executes no code or commands, and makes no financial transactions. It is a pure read operation that queries a disaster information system.
From the tool's definition Tool name 'get_disaster_statistics' and description 'Get disaster statistics aggregated by event type and alert level' indicate a retrieval operation that queries and aggregates existing data from www.gdacs.org without modification, deletion, or execution of…
Attacks that exploit this kind of access
Get disaster statistics aggregated by event type and alert level for a specified time period. It is categorised as a Read tool in the Api MCP Server, which means it retrieves data without modifying state.
get_disaster_statistics accepts 5 parameters: toDate, country, fromDate, alertLevel, 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_disaster_statistics: 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_disaster_statistics 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_disaster_statistics 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_disaster_statistics. 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_disaster_statistics 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 →