Get recent tweets from a specific Twitter/X user.
AI agents call get_twitter_user_tweets to retrieve information from Twitter 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 publicly available tweet data from a user's timeline. It performs a read-only query operation with no ability to modify, delete, or execute actions. The blast radius is minimal—an AI agent misusing this tool could retrieve unwanted user data but cannot cause irreversible harm, financial impact, or execute code. Classification as Read is appropriate.
From the tool's definition Tool name 'get_twitter_user_tweets' and description 'Get recent tweets from a specific Twitter/X user' indicate data retrieval with no modification or side effects.
Attacks that exploit this kind of access
Get recent tweets from a specific Twitter/X user. It is categorised as a Read tool in the Twitter MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Twitter MCP Server MCP server in PolicyLayer and add a rule for get_twitter_user_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 Twitter MCP Server. Nothing to install.
get_twitter_user_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 get_twitter_user_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 get_twitter_user_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.
get_twitter_user_tweets is provided by the Twitter MCP Server MCP server (kamflowersthemacrogod/opentwitter-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 →