Fetch tweets from a specific user
AI agents call get_user_tweets to retrieve information from Agent Twitter Client without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves existing tweet data from a user's timeline. It performs a query operation that does not modify, delete, or execute any actions. The verb 'Fetch' and the lack of any modification capability place it squarely in the Read category. Severity is low because retrieving publicly available tweet data poses minimal risk even if misused by an agent.
From the tool's definition Tool name 'get_user_tweets' and description 'Fetch tweets from a specific user' indicate data retrieval with no side effects.
Attacks that exploit this kind of access
Fetch tweets from a specific user. It is categorised as a Read tool in the Agent Twitter Client MCP Server, which means it retrieves data without modifying state.
Register the Agent Twitter Client MCP server in PolicyLayer and add a rule for get_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 Agent Twitter Client. Nothing to install.
get_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_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_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_user_tweets is provided by the Agent Twitter Client MCP server (theo-nash/twitter-mcp-server). 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 →