Low Risk

search_twitter

Search Twitter with a query

How to control search_twitter ↓

AI agents call search_twitter to retrieve information from X (Twitter) MCP server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Low Risk

Searching Twitter retrieves publicly available or user-accessible tweets matching a query. This is a read-only operation with no capability to modify, delete, or execute actions. While the sibling tools include destructive operations (delete_tweet, delete_all_bookmarks), this tool itself only queries and returns results.

From the tool's definition Tool name 'search_twitter' with description 'Search Twitter with a query' indicates a query operation that retrieves data without side effects.

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

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

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

search_twitter 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 X (Twitter) MCP server — 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.

Go deeper

What does the search_twitter tool do? +

Search Twitter with a query. It is categorised as a Read tool in the X (Twitter) MCP server MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on search_twitter? +

Register the X (Twitter) MCP server MCP server in PolicyLayer and add a rule for search_twitter: 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) MCP server. Nothing to install.

What risk level is search_twitter? +

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

Can I rate-limit search_twitter? +

Yes. Add a rate_limit block to the search_twitter 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 search_twitter completely? +

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

search_twitter is provided by the X (Twitter) MCP server MCP server (rafaljanicki/x-twitter-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every X (Twitter) MCP server tool call.

Deterministic rules across all 24 X (Twitter) MCP server tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

Free to start. No card required.

24 X (Twitter) MCP server tools catalogued and risk-classified — across an index of 42,500+ 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.