This record as markdown: /tools/ghl/delete-conversation.md
What delete_conversation does on Ghl
AI agents call delete_conversation to permanently remove resources in Ghl, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
| Parameter | Type | Required | Description |
|---|---|---|---|
conversationId | string | Yes | The unique ID of the conversation to delete |
Parameters from the server's own tool schema.
Why delete_conversation is rated Critical
This tool performs a permanent, irreversible deletion operation on conversation data. Permanent deletion qualifies as Destructive under the classification rules. The high severity reflects the risk that an AI agent could inadvertently or maliciously erase important business communications and records without recovery options.
From the tool's definition Tool name 'delete_conversation' combined with description 'Delete a conversation permanently' explicitly indicates irreversible deletion of data.
Attacks that exploit this kind of access
The rule that runs delete_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 delete_conversation, this is the rule to start with:
delete_conversation is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.
The button opens the PolicyLayer dashboard: create your workspace, connect Ghl, apply this rule, and every delete_conversation call is checked against it from then on.
Questions about delete_conversation
Delete a conversation permanently. It is categorised as a Destructive tool in the Ghl MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
delete_conversation accepts 1 parameter: 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 delete_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.
delete_conversation is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the delete_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 delete_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.
delete_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.
Across the catalogue