AI agents call gdelt_geo_events to retrieve information from UnClick without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
query | string | Yes | Topic or keyword to map |
timespan | string | — | Time window (e.g. '24h', '7d') |
maxpoints | number | — | Max location clusters to return (default 50, max 250) |
Parameters from the server's own tool schema.
This tool queries the GDELT GEO API to retrieve and aggregate publicly available news event data. It performs a read-only operation that retrieves structured information about news events without any side effects, reversible modifications, code execution, data destruction, or financial transactions. The worst plausible misuse is retrieving unwanted but non-harmful geographic news data.
From the tool's definition Tool description states it 'Get[s] geographic distribution of news events' and 'Returns event clusters with location, article count, and tone score.' The verbs 'get' and 'returns' indicate data retrieval with no modification, creation, deletion, execution, or…
Risk signalsAccepts freeform code/query input (query)
Attacks that exploit this kind of access
Get geographic distribution of news events for a topic from the GDELT GEO API. Returns event clusters with location, article count, and tone score. It is categorised as a Read tool in the UnClick MCP Server, which means it retrieves data without modifying state.
gdelt_geo_events accepts 3 parameters: query, timespan, maxpoints. Required: query. The full parameter table on this page comes from the server's own tool schema.
Register the UnClick MCP server in PolicyLayer and add a rule for gdelt_geo_events: 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 UnClick. Nothing to install.
gdelt_geo_events 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 gdelt_geo_events 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 gdelt_geo_events. 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.
gdelt_geo_events is provided by the UnClick MCP server (@unclick/mcp-server). 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 →