get_conversation
Get detailed conversation information including message history
This record as markdown: /tools/ghl/get-conversation.md
What get_conversation does on Ghl
AI agents call get_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 |
|---|---|---|---|
limit | number | — | Maximum number of messages to return (default: 20) |
messageTypes | array | — | Filter messages by type (optional) |
conversationId | string | Yes | The unique ID of the conversation to retrieve |
Parameters from the server's own tool schema.
Why get_conversation is rated Low
This tool retrieves and queries existing conversation data and message history. It performs no creation, modification, deletion, code execution, or financial operations. It is a straightforward read operation with minimal risk if an AI agent calls it, as the only exposure would be unauthorized access to conversation data (a data privacy concern rather than a system integrity or destructive risk).
From the tool's definition Tool name is 'get_conversation' and description states 'Get detailed conversation information including message history' — both indicate data retrieval with no modification or side effects.
Attacks that exploit this kind of access
The rule that runs get_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 get_conversation, this is the rule to start with:
get_conversation 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 get_conversation call is checked against it from then on.
Questions about get_conversation
Get detailed conversation information including message history. It is categorised as a Read tool in the Ghl MCP Server, which means it retrieves data without modifying state.
get_conversation accepts 3 parameters: limit, messageTypes, conversationId. Required: conversationId. 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 get_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.
get_conversation 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_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.
Set action: deny in the PolicyLayer policy for get_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.
get_conversation 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