Get casts from a specific Farcaster user by FID
AI agents call get-user-casts 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 retrieves publicly available cast data from the Farcaster network based on a user identifier. It performs a query-only operation that does not create, modify, delete, or execute any external actions. The action has no side effects and aligns with the 'Read' category of data retrieval tools. Severity is low because misuse would only expose existing public information without enabling harmful operations.
From the tool's definition Tool name 'get-user-casts' and description 'Get casts from a specific Farcaster user by FID' indicate a retrieval operation with no modification or side effects.
Attacks that exploit this kind of access
Get casts from a specific Farcaster user by FID. 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-casts: 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-casts 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-casts 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-casts. 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-casts 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 →