get_twitter_user
Get Twitter/X user profile information by username.
This record as markdown: /tools/6551team-opentwitter-mcp/get-twitter-user.md
What get_twitter_user does on Twitter MCP Server
AI agents call get_twitter_user to retrieve information from Twitter MCP Server without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why get_twitter_user is rated Low
This tool retrieves user profile information, which is a read-only operation. It queries existing data without creating, modifying, deleting, or executing any actions. The severity is low because user profile information is typically public on Twitter/X and exposure of this retrieval capability poses minimal risk to users or systems.
From the tool's definition Tool name 'get_twitter_user' and description 'Get Twitter/X user profile information by username' indicate retrieval of publicly available profile data with no modification or side effects.
Attacks that exploit this kind of access
The rule that runs get_twitter_user safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Twitter MCP Server, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For get_twitter_user, this is the rule to start with:
get_twitter_user 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 Twitter MCP Server, apply this rule, and every get_twitter_user call is checked against it from then on.
Questions about get_twitter_user
Get Twitter/X user profile information by username. 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: 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 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 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. 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 is provided by the Twitter MCP Server MCP server (6551team/opentwitter-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Twitter MCP Server, and thousands of servers like it.
This server
Across the catalogue