Searches Threads posts by keyword. Args: - threads_user_id (string): Threads user ID (for auth context) - q (string): Search query - limit (number): Max results (default 20) Note: Results are limited to the authenticated user
AI agents call threads_search 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/queries existing Threads posts based on search criteria. It has no side effects—it does not create, modify, delete, execute code, or commit financial transactions. The scope limitation to authenticated user results further reduces risk. This is a straightforward Read category tool with low severity.
From the tool's definition Tool name 'threads_search' and description 'Searches Threads posts by keyword' indicate a query/retrieval operation. The arguments (threads_user_id, q, limit) are typical for a search function.
Documented attack patterns abuse exactly the kind of access threads_search 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_search:
{
"version": "1",
"default": "deny",
"tools": {
"threads_search": {}
}
}threads_search 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.
Searches Threads posts by keyword. Args: - threads_user_id (string): Threads user ID (for auth context) - q (string): Search query - limit (number): Max results (default 20) Note: Results are limited to the authenticated user. 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_search: 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_search 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_search 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_search. 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_search 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.