Search public Threads posts by keyword using the official keyword_search endpoint.
AI agents call search_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 and queries public data without side effects. It does not create, modify, delete, or execute any operations. It simply searches and returns matching Threads posts, which is a classic Read operation with minimal security risk.
From the tool's definition Tool description explicitly states it 'Search[es] public Threads posts by keyword' and uses the 'keyword_search endpoint'. The function is purely informational retrieval with no modification, deletion, or execution capabilities.
Attacks that exploit this kind of access
Search public Threads posts by keyword using the official keyword_search endpoint. 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 search_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.
search_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 search_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 search_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.
search_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 →