Get the list of users that a Farcaster user follows
AI agents call get-user-following to retrieve information from Farcaster MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries and retrieves social graph data (following relationships) from the Farcaster network without creating, modifying, deleting, or executing any operations. It is a passive information retrieval endpoint similar to sibling tools like 'get-user-profile' and 'get-user-followers'.
From the tool's definition Tool name 'get-user-following' and description 'Get the list of users that a Farcaster user follows' indicate a retrieval operation with no side effects. The verb 'get' and lack of any modification or execution language confirm read-only behavior.
Attacks that exploit this kind of access
Get the list of users that a Farcaster user follows. It is categorised as a Read tool in the Farcaster MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Farcaster MCP Server MCP server in PolicyLayer and add a rule for get-user-following: 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 Farcaster MCP Server. Nothing to install.
get-user-following 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-following 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-following. 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-following is provided by the Farcaster MCP Server MCP server (manimohans/farcaster-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 →