AI agents call search_tweets 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.
Search operations retrieve and query data without modifying, deleting, or executing external actions. Despite the empty description, the function name and context from related tools (all retrieval-focused) strongly indicate this is a read operation with minimal blast radius. Confidence reduced slightly due to missing tool description, but the naming and server context are clear.
From the tool's definition Tool name 'search_tweets' indicates a query operation. The server description confirms it 'retrieve[s] tweets' programmatically.
Documented attack patterns abuse exactly the kind of access search_tweets 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 search_tweets:
{
"version": "1",
"default": "deny",
"tools": {
"search_tweets": {}
}
} search_tweets 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.
search_tweets. 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 search_tweets: 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.
search_tweets 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 search_tweets 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 search_tweets. 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.
search_tweets 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.