gdelt_trending
Check whether a topic is trending in global news using GDELT article volume timelines. Returns a trend classification (surging, rising, stable, declining, fading) and volume data over time.
This record as markdown: /tools/io-github-malamutemayhem-unclick-mcp-server/gdelt-trending.md
What gdelt_trending does on UnClick
AI agents call gdelt_trending to retrieve information from UnClick 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 |
|---|---|---|---|
query | string | Yes | Topic or keyword to check |
timespan | string | — | Time window (e.g. '24h', '7d', '1month') |
sourcelang | string | — | Filter by source language |
Parameters from the server's own tool schema.
Why gdelt_trending is rated Low
This is a read-only query tool that fetches and classifies existing news trend data from GDELT. It does not create, modify, delete, execute arbitrary operations, or involve financial transactions. The blast radius of misuse is minimal — an agent could only obtain trending information, which has no destructive or costly consequences.
From the tool's definition The tool "Check whether a topic is trending in global news using GDELT article volume timelines" retrieves and analyzes data without modifying any state.
Attacks that exploit this kind of access
The rule that runs gdelt_trending safely
PolicyLayer is an MCP gateway: it sits between your AI agents and UnClick, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For gdelt_trending, this is the rule to start with:
gdelt_trending 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 UnClick, apply this rule, and every gdelt_trending call is checked against it from then on.
Questions about gdelt_trending
Check whether a topic is trending in global news using GDELT article volume timelines. Returns a trend classification (surging, rising, stable, declining, fading) and volume data over time. It is categorised as a Read tool in the UnClick MCP Server, which means it retrieves data without modifying state.
gdelt_trending accepts 3 parameters: query, timespan, sourcelang. 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_trending: 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_trending 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_trending 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_trending. 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_trending 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.
More on UnClick, and thousands of servers like it.
This server
Across the catalogue