conversations_search_conversation

Search Conversations

SERVERGhl SOURCE@aiwerk/mcp-server-ghl

Low RISK CLASS

Category Read

Parameters 120 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/aiwerk-mcp-server-ghl/conversations-search-conversation.md

WHAT IT DOES

What conversations_search_conversation does on Ghl

AI agents call conversations_search_conversation 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
`id`	string	—	Id of the conversation
`sort`	string	—	Sort paramater - asc or desc
`limit`	number	—	Limit of conversations - Default is 20
`query`	string	—	Search paramater as a string
`sortBy`	string	—	The sorting of the conversation to be filtered as - manual messages or all messages
`status`	string	—	The status of the conversation to be filtered - all, read, unread, starred
`endDate`	number	—	End date filter for dateAdded field (Unix timestamp in milliseconds)
`mentions`	string	—	User Id of the mention. Multiple values are comma separated.
`contactId`	string	—	Contact Id
`followers`	string	—	User IDs of followers to filter conversations by. Multiple IDs can be provided as comma-separated values.
`startDate`	number	—	Start date filter for dateAdded field (Unix timestamp in milliseconds)
`assignedTo`	string	—	User IDs that conversations are assigned to. Multiple IDs can be provided as comma-separated values. Use "unassigned" to fetch conversations not assigned to any

Parameters from the server's own tool schema.

RISK

Why conversations_search_conversation is rated Low

Even though conversations_search_conversation only reads data, uncontrolled read access leaks sensitive information and racks up API costs: an agent caught in a retry loop can make thousands of calls a minute without anyone noticing.

Risk signalsHigh parameter count (21 properties)

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs conversations_search_conversation 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 conversations_search_conversation, this is the rule to start with:

conversations_search_conversation Allowed

conversations_search_conversation is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "conversations_search_conversation": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Ghl, apply this rule, and every conversations_search_conversation call is checked against it from then on.

FAQ

Questions about conversations_search_conversation

What does the conversations_search_conversation tool do? +

Search Conversations. It is categorised as a Read tool in the Ghl MCP Server, which means it retrieves data without modifying state.

What parameters does conversations_search_conversation accept? +

conversations_search_conversation accepts 12 parameters: id, sort, limit, query, sortBy, status, endDate, mentions, contactId, followers, startDate, assignedTo. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on conversations_search_conversation? +

Register the Ghl MCP server in PolicyLayer and add a rule for conversations_search_conversation: 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.

What risk level is conversations_search_conversation? +

conversations_search_conversation is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit conversations_search_conversation? +

Yes. Add a rate_limit block to the conversations_search_conversation 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.

How do I block conversations_search_conversation completely? +

Set action: deny in the PolicyLayer policy for conversations_search_conversation. 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.

What MCP server provides conversations_search_conversation? +

conversations_search_conversation is provided by the Ghl MCP server (@aiwerk/mcp-server-ghl). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Ghl, and thousands of servers like it.

This server

All 569 Ghl tools →

Across the catalogue

evaluate_search_quality on ACE-MCP →search_torrents on M-Team MCP Server →aiva_search_customers on AIVA MCP Server →search_channel on YouTube MCP Server → The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →