search_conversations
Search conversations in GoHighLevel with various filters
This record as markdown: /tools/ghl/search-conversations.md
What search_conversations does on Ghl
AI agents call search_conversations to retrieve information from Ghl without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
limit | number | — | Maximum number of conversations to return (default: 20, max: 100) |
query | string | — | Search query to filter conversations |
status | string | — | Filter conversations by read status |
contactId | string | — | Filter conversations for a specific contact |
assignedTo | string | — | Filter by user ID assigned to conversations |
Parameters from the server's own tool schema.
Why search_conversations is rated Low
This tool queries and retrieves conversation data from the GoHighLevel CRM system using filters. It has no side effects—it does not create, modify, delete, or execute actions. It is a straightforward read operation that returns filtered results.
From the tool's definition Tool name 'search_conversations' and description 'Search conversations in GoHighLevel with various filters' indicate data retrieval without modification. The verb 'search' is a read-only operation.
Risk signalsAccepts freeform code/query input (query)
Attacks that exploit this kind of access
The rule that runs search_conversations safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Ghl, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For search_conversations, this is the rule to start with:
search_conversations is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Ghl, apply this rule, and every search_conversations call is checked against it from then on.
Questions about search_conversations
Search conversations in GoHighLevel with various filters. It is categorised as a Read tool in the Ghl MCP Server, which means it retrieves data without modifying state.
search_conversations accepts 5 parameters: limit, query, status, contactId, assignedTo. The full parameter table on this page comes from the server's own tool schema.
Register the Ghl MCP server in PolicyLayer and add a rule for search_conversations: 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 Ghl. Nothing to install.
search_conversations 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_conversations 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_conversations. 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_conversations is provided by the Ghl MCP server (ghl-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Ghl, and thousands of servers like it.
This server
Across the catalogue