Lists followers of the authenticated Threads user. Args: - threads_user_id (string): Threads user ID - limit (number): Max results (1–100, default 25) - after (string, optional): Pagination cursor Returns: User IDs, usernames, and profile picture URLs of followers. Note: Requires threads_basic sc...
AI agents call threads_get_followers to retrieve information from Meta 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 follower information without modifying data, executing commands, or creating side effects. It is a straightforward read operation with scope restrictions (threads_basic) and user privacy controls (only visible followers returned). The blast radius of misuse is limited to unauthorized visibility of public follower lists, making it low severity.
From the tool's definition Tool name 'threads_get_followers' and description 'Lists followers' indicate pure data retrieval. Returns 'User IDs, usernames, and profile picture URLs' with no mention of modification, deletion, or state changes.
Documented attack patterns abuse exactly the kind of access threads_get_followers gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Meta MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for threads_get_followers:
{
"version": "1",
"default": "deny",
"tools": {
"threads_get_followers": {}
}
}threads_get_followers 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.
Lists followers of the authenticated Threads user. Args: - threads_user_id (string): Threads user ID - limit (number): Max results (1–100, default 25) - after (string, optional): Pagination cursor Returns: User IDs, usernames, and profile picture URLs of followers. Note: Requires threads_basic scope. Only returns users who have allowed their followers list to be visible. It is categorised as a Read tool in the Meta MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Meta MCP Server MCP server in PolicyLayer and add a rule for threads_get_followers: 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 Meta MCP Server. Nothing to install.
threads_get_followers 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 threads_get_followers 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 threads_get_followers. 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.
threads_get_followers is provided by the Meta MCP Server MCP server (oliverames/meta-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Meta MCP Server, 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.
200 Meta MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.