getXUserTweets
Get recent tweets from a specific X/Twitter user by their user ID. Use getXUserByUsername first to get the user ID from a handle.
This record as markdown: /tools/nanidao-agentek/getxusertweets.md
What getXUserTweets does on Agentek Eth
AI agents call getXUserTweets to retrieve information from Agentek Eth without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why getXUserTweets is rated Low
This tool performs data retrieval only—fetching historical tweets from a public social media source. It has no side effects on the Ethereum/crypto systems or any other data. No financial transactions, modifications, or destructive operations are possible. The blast radius of misuse is minimal; an AI agent could fetch tweets repetitively or excessively, but cannot cause permanent harm or financial loss.
From the tool's definition Tool retrieves tweets from a specific X/Twitter user by user ID. The description uses 'Get' (retrieval verb) and indicates query-like behavior with no mention of modification, deletion, or side effects.
Attacks that exploit this kind of access
The rule that runs getXUserTweets safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Agentek Eth, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For getXUserTweets, this is the rule to start with:
getXUserTweets is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Agentek Eth, apply this rule, and every getXUserTweets call is checked against it from then on.
Questions about getXUserTweets
Get recent tweets from a specific X/Twitter user by their user ID. Use getXUserByUsername first to get the user ID from a handle. It is categorised as a Read tool in the Agentek Eth MCP Server, which means it retrieves data without modifying state.
Register the Agentek Eth MCP server in PolicyLayer and add a rule for getXUserTweets: 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 Agentek Eth. Nothing to install.
getXUserTweets 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 getXUserTweets 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 getXUserTweets. 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.
getXUserTweets is provided by the Agentek Eth MCP server (nanidao/agentek). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Agentek Eth, and thousands of servers like it.
This server
Across the catalogue