Return a paginated list of public posts for an exact Threads username.
AI agents call get_profile_threads to retrieve information from Threads 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 public, already-published thread data. It has no side effects—it neither modifies, deletes, nor executes operations. The data is public by definition (posts visible to the username's followers or public profile). The blast radius of misuse is minimal; an agent could enumerate posts but cannot alter them or cause harm beyond reading publicly available information.
From the tool's definition Tool returns a paginated list of public posts for a Threads username. The description uses "Return" and "list" indicating data retrieval with no modification or deletion of data.
Attacks that exploit this kind of access
Return a paginated list of public posts for an exact Threads username. It is categorised as a Read tool in the Threads MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Threads MCP Server MCP server in PolicyLayer and add a rule for get_profile_threads: 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 Threads MCP Server. Nothing to install.
get_profile_threads 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_profile_threads 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_profile_threads. 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_profile_threads is provided by the Threads MCP Server MCP server (poisonstefani-dev/threads-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 →