Get Twitter user info by username. Returns cleaned data in TOON format.
AI agents call get_user_by_username to retrieve information from TwitterAPI MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries and retrieves publicly available Twitter user profile data. It performs a read-only operation that does not create, modify, delete, or execute any actions. The blast radius of misuse is minimal—an attacker could gather user information but cannot alter data, delete accounts, post content, or trigger external operations. Severity is low because Twitter user profiles are typically public information.
From the tool's definition Tool name 'get_user_by_username' and description 'Get Twitter user info by username' indicate data retrieval with no modification or destructive capability. Returns user profile information without side effects.
Attacks that exploit this kind of access
Get Twitter user info by username. Returns cleaned data in TOON format. It is categorised as a Read tool in the TwitterAPI MCP Server MCP Server, which means it retrieves data without modifying state.
Register the TwitterAPI MCP Server MCP server in PolicyLayer and add a rule for get_user_by_username: 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 TwitterAPI MCP Server. Nothing to install.
get_user_by_username 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_by_username 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_by_username. 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_by_username is provided by the TwitterAPI MCP Server MCP server (jing-yilin/twitterapi-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 →