Follow a user on Twitter/X by their numerical Twitter ID (TWID). If you only have a username, use get_user_details first to get the TWID.
AI agents use follow_user to create or update resources in Apex MCP for X Management — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Apex MCP for X Management environment.
Following a user creates a new social relationship on the platform. This is a reversible write operation (can be undone by unfollowing), not destructive or financial. Misuse could lead to unwanted follows at scale, which could damage account reputation or trigger spam detection.
From the tool's definition Follow a user on Twitter/X by their numerical Twitter ID (TWID)
Attacks that exploit this kind of access
Follow a user on Twitter/X by their numerical Twitter ID (TWID). If you only have a username, use get_user_details first to get the TWID. It is categorised as a Write tool in the Apex MCP for X Management MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Apex MCP for X Management MCP server in PolicyLayer and add a rule for follow_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 Apex MCP for X Management. Nothing to install.
follow_user is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the follow_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 follow_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.
follow_user 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 →