Get comprehensive user profile information by username or Twitter ID. Returns full user object including numerical Twitter ID (TWID), follower/following counts, verification status, profile image/banner, bio description, location, creation date, tweet counts, and more. Use this tool only when you...
AI agents call get_user_details to retrieve information from Apex MCP for X Management without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This is a pure data retrieval tool that queries public user profile metadata. While it returns sensitive information (follower counts, verification status, profile details), it does not modify data, execute code, or have destructive effects.
From the tool's definition Tool retrieves and returns user profile information (TWID, follower/following counts, verification status, profile image/banner, bio, location, creation date, tweet counts) with no modification stated.
Attacks that exploit this kind of access
Get comprehensive user profile information by username or Twitter ID. Returns full user object including numerical Twitter ID (TWID), follower/following counts, verification status, profile image/banner, bio description, location, creation date, tweet counts, and more. Use this tool only when you need the TWID for follow/unfollow operations or want detailed profile information. It is categorised as a Read tool in the Apex MCP for X Management MCP Server, which means it retrieves data without modifying state.
Register the Apex MCP for X Management MCP server in PolicyLayer and add a rule for get_user_details: 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 Apex MCP for X Management. Nothing to install.
get_user_details 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_details 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_details. 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_details is provided by the Apex MCP for X Management MCP server (xonack/apex-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 →