twitter.trends.worldwide
Get current trending topics on Twitter/X. Filter by location using WOEID (Where On Earth ID). Returns trend name, search query, and rank. 1=worldwide, 23424977=US, 23424975=UK.
This record as markdown: /tools/io-github-whiteknightonhorse-apibase/twitter.trends.worldwide.md
What twitter.trends.worldwide does on Apibase
AI agents call twitter.trends.worldwide to retrieve information from Apibase 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 |
|---|---|---|---|
woeid | integer | — | Where On Earth ID for location-specific trends (1=worldwide, 23424977=US, 23424975=UK, 23424856=Japan) |
Parameters from the server's own tool schema.
Why twitter.trends.worldwide is rated Low
Tool queries public Twitter/X trending data with no write, execute, or financial side effects.
From the tool's definition Get current trending topics on Twitter/X. Filter by location, returns trend name, search query, and rank.
Attacks that exploit this kind of access
The rule that runs twitter.trends.worldwide safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Apibase, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For twitter.trends.worldwide, this is the rule to start with:
twitter.trends.worldwide 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 Apibase, apply this rule, and every twitter.trends.worldwide call is checked against it from then on.
Questions about twitter.trends.worldwide
Get current trending topics on Twitter/X. Filter by location using WOEID (Where On Earth ID). Returns trend name, search query, and rank. 1=worldwide, 23424977=US, 23424975=UK. It is categorised as a Read tool in the Apibase MCP Server, which means it retrieves data without modifying state.
twitter.trends.worldwide accepts 1 parameter: woeid. The full parameter table on this page comes from the server's own tool schema.
Register the Apibase MCP server in PolicyLayer and add a rule for twitter.trends.worldwide: 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 Apibase. Nothing to install.
twitter.trends.worldwide 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 twitter.trends.worldwide 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 twitter.trends.worldwide. 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.
twitter.trends.worldwide is provided by the Apibase MCP server (apibase-mcp-client). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Apibase, and thousands of servers like it.
This server
Across the catalogue