AI agents call get_event_data 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 |
|---|---|---|---|
eventId | integer | Yes | Numeric event identifier from GDACS |
eventType | string | Yes | Event type code: EQ (Earthquake), TC (Tropical Cyclone), FL (Flood), VO (Volcano), WF (Wildfire), DR (Drought) |
Parameters from the server's own tool schema.
This tool retrieves and queries disaster event information from a public web-based system (www.gdacs.org). It has no side effects, does not modify data, execute commands, or trigger external operations. The data returned (location, severity, affected population, timeline) is informational only.
From the tool's definition Tool name 'get_event_data' and description explicitly states it 'Get detailed information about a specific disaster event' and 'Returns event data' — indicating data retrieval with no modification or execution capability.
Attacks that exploit this kind of access
Get detailed information about a specific disaster event. Returns event data including location, severity, affected population, and timeline. It is categorised as a Read tool in the Api MCP Server, which means it retrieves data without modifying state.
get_event_data accepts 2 parameters: eventId, eventType. Required: eventId, eventType. 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_event_data: 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_event_data 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_event_data 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_event_data. 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_event_data 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 →