Low Risk

get_trends

Get trending topics by category.

How to control get_trends ↓

What get_trends does on Twikit

AI agents call get_trends to retrieve information from Twikit without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Low Risk

Why get_trends needs a policy

This tool only retrieves publicly available trending topic information. It has no side effects, does not modify data, execute code, or commit any financial or destructive actions. The read-only nature and public data source make it the lowest severity, though operating within a Twitter/X client with authentication could potentially enable social engineering if trends data is misused in context of other capabilities.

From the tool's definition Tool name 'get_trends' and description 'Get trending topics by category' indicate a read-only query operation that retrieves public trending data without modifying or executing actions.

Documented attack patterns abuse exactly the kind of access get_trends gives an agent:

How to control get_trends

PolicyLayer is an MCP gateway — it sits between your AI agents and Twikit, and nothing reaches the server without passing your rules. This is the rule we recommend for get_trends:

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "get_trends": {}
  }
}

get_trends is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.

  1. Create a free account and register Twikit — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
CAP THIS TOOL →

Free to start. No card required.

Related tools and policies

Go deeper

Questions about get_trends

What does the get_trends tool do? +

Get trending topics by category. It is categorised as a Read tool in the Twikit MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get_trends? +

Register the Twikit MCP server in PolicyLayer and add a rule for get_trends: 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 Twikit. Nothing to install.

What risk level is get_trends? +

get_trends is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit get_trends? +

Yes. Add a rate_limit block to the get_trends 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.

How do I block get_trends completely? +

Set action: deny in the PolicyLayer policy for get_trends. 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.

What MCP server provides get_trends? +

get_trends is provided by the Twikit MCP server (tangivis/twitter-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Twikit tool call.

Start from Twikit, 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.

59 Twikit tools catalogued and risk-classified — across an index of 43,000+ MCP servers.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.