Get the users that a Twitter user is following
AI agents call getTwitterFollowing to retrieve information from Twitter Client MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves follower relationship information, which is a read-only operation with no side effects. It does not create, modify, delete, or execute any irreversible actions. The data returned is typically public information on social media platforms. Risk is minimal unless the retrieved data is used downstream for harmful purposes, but the tool itself is purely informational.
From the tool's definition Tool name and description both indicate this is a retrieval operation: 'Get the users that a Twitter user is following'. It queries and returns follower relationship data without modifying, deleting, or executing actions.
Documented attack patterns abuse exactly the kind of access getTwitterFollowing gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Twitter Client MCP, and nothing reaches the server without passing your rules. This is the rule we recommend for getTwitterFollowing:
{
"version": "1",
"default": "deny",
"tools": {
"getTwitterFollowing": {}
}
}getTwitterFollowing is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Get the users that a Twitter user is following. It is categorised as a Read tool in the Twitter Client MCP MCP Server, which means it retrieves data without modifying state.
Register the Twitter Client MCP server in PolicyLayer and add a rule for getTwitterFollowing: 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 Client MCP. Nothing to install.
getTwitterFollowing 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 getTwitterFollowing 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 getTwitterFollowing. 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.
getTwitterFollowing is provided by the Twitter Client MCP server (mzkrasner/twitter-client-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Twitter Client MCP, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
20 Twitter Client MCP tools catalogued and risk-classified — across an index of 43,000+ MCP servers.