Get Twitter/X user profile information by user ID.
AI agents call get_twitter_user_by_id to retrieve information from Twitter MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This is a simple profile lookup operation that queries public or authorized user data from Twitter/X. It has no capability to modify data, execute code, delete information, or commit financial obligations. The blast radius is minimal as it only returns existing user profile information. Confidence is high due to clear Read semantics.
From the tool's definition Tool retrieves 'Twitter/X user profile information' by user ID with no modification capability. The description contains retrieves/query language ('Get') with no mention of side effects, creation, modification, deletion, or execution.
Attacks that exploit this kind of access
Get Twitter/X user profile information by user ID. 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_by_id: 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_by_id 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_by_id 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_by_id. 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_by_id is provided by the Twitter MCP Server MCP server (kamflowersthemacrogod/opentwitter-mcp). 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 →