AI agents call get_trending_topics to retrieve information from X(Twitter) V2 MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The tool retrieves publicly available trending topics data with no side effects, no data modification, and no external state changes. This is a simple information retrieval operation. Severity is low because misuse poses minimal risk (querying trends cannot harm users, accounts, or systems). High confidence despite empty description due to clear naming convention matching sibling Read-category tools.
From the tool's definition Tool named 'get_trending_topics' with empty description. By name and context (sibling tools like get_tweet_by_id, get_tweets_by_userid, get_user_by_username that retrieve data), this retrieves trending topic information—a read-only query operation.
Documented attack patterns abuse exactly the kind of access get_trending_topics gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and X(Twitter) V2 MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for get_trending_topics:
{
"version": "1",
"default": "deny",
"tools": {
"get_trending_topics": {}
}
}get_trending_topics is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
get_trending_topics. It is categorised as a Read tool in the X(Twitter) V2 MCP Server MCP Server, which means it retrieves data without modifying state.
Register the X(Twitter) V2 MCP Server MCP server in PolicyLayer and add a rule for get_trending_topics: 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 X(Twitter) V2 MCP Server. Nothing to install.
get_trending_topics 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_trending_topics 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_trending_topics. 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_trending_topics is provided by the X(Twitter) V2 MCP Server MCP server (nexusx-mcp/x-v2-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from X(Twitter) V2 MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
16 X(Twitter) V2 MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.