getXUserByUsername
Look up an X/Twitter user by their username/handle. Returns their profile info, follower counts, and bio.
This record as markdown: /tools/nanidao-agentek/getxuserbyusername.md
What getXUserByUsername does on Agentek Eth
AI agents call getXUserByUsername 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 getXUserByUsername is rated Low
This tool retrieves publicly available user profile data from X/Twitter. It performs a query-like operation with no side effects, data modification, or code execution. The impact of misuse is minimal (e.g., gathering OSINT on a user), making severity low.
From the tool's definition Tool description states it 'Look up' and 'Returns their profile info, follower counts, and bio' — purely retrieval operations with no modification, deletion, or execution of code/commands.
Attacks that exploit this kind of access
The rule that runs getXUserByUsername 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 getXUserByUsername, this is the rule to start with:
getXUserByUsername 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 getXUserByUsername call is checked against it from then on.
Questions about getXUserByUsername
Look up an X/Twitter user by their username/handle. Returns their profile info, follower counts, and bio. 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 getXUserByUsername: 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.
getXUserByUsername 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 getXUserByUsername 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 getXUserByUsername. 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.
getXUserByUsername 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