AI agents call get_tweets_by_userid 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.
This tool retrieves/queries tweet data with no side effects or state modifications. It follows the Read category pattern of other query tools on the same server. The empty description lowers confidence slightly, but the name and context provide sufficient evidence. Low severity because unauthorized tweet retrieval has minimal blast radius compared to posting or deletion.
From the tool's definition Tool name 'get_tweets_by_userid' indicates retrieval of tweets by a user identifier. Sibling tools include 'get_tweet_by_id', 'get_user_by_username', and 'get_user_mentions'—all clearly Read operations.
Documented attack patterns abuse exactly the kind of access get_tweets_by_userid 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_tweets_by_userid:
{
"version": "1",
"default": "deny",
"tools": {
"get_tweets_by_userid": {}
}
}get_tweets_by_userid 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_tweets_by_userid. 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_tweets_by_userid: 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_tweets_by_userid 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_tweets_by_userid 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_tweets_by_userid. 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_tweets_by_userid 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.