Advanced Twitter/X search tool for finding tweets with powerful filtering capabilities. Returns tweets matching your criteria, sorted by relevance or time. Expect 2-5 second response times. Note: API may return duplicate entries - this is normal behavior. IMPORTANT: There is no
AI agents call search_tweets to retrieve information from Apex MCP for X Management without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The search_tweets tool performs a query operation to retrieve existing tweets based on filter criteria. It has no side effects, does not modify data, does not execute code, and does not delete or move resources. It is a straightforward read operation. The low severity reflects that misuse would at most return unwanted tweet data, with no destructive or financial impact.
From the tool's definition Tool is described as 'Advanced Twitter/X search tool for finding tweets' that 'Returns tweets matching your criteria.' This is a retrieval operation with no mention of creation, modification, deletion, or execution capabilities.
Attacks that exploit this kind of access
Advanced Twitter/X search tool for finding tweets with powerful filtering capabilities. Returns tweets matching your criteria, sorted by relevance or time. Expect 2-5 second response times. Note: API may return duplicate entries - this is normal behavior. IMPORTANT: There is no. It is categorised as a Read tool in the Apex MCP for X Management MCP Server, which means it retrieves data without modifying state.
Register the Apex MCP for X Management 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 Apex MCP for X Management. 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 Apex MCP for X Management MCP server (xonack/apex-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →