Delete a conversation permanently
AI agents call delete_conversation to permanently remove resources in GoHighLevel MCP Server — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
This tool irreversibly deletes data (conversations) with no undo capability. The word 'permanently' explicitly indicates the action cannot be reversed. While the blast radius is high (loss of communication history), it does not involve financial transactions or direct code execution, making Destructive the correct category rather than Financial or Execute.
From the tool's definition delete_conversation: Delete a conversation permanently
Documented attack patterns abuse exactly the kind of access delete_conversation gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and GoHighLevel MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for delete_conversation:
{
"version": "1",
"default": "deny",
"hide": [
"delete_conversation"
]
} delete_conversation disappears from the agent's tool list entirely, and any attempt to call it is denied. The rest of the server keeps working.
Free to start. No card required.
Delete a conversation permanently. It is categorised as a Destructive tool in the GoHighLevel MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the GoHighLevel MCP Server 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 GoHighLevel MCP Server. 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 GoHighLevel MCP Server MCP server (busybee3333/go-high-level-mcp-2026-complete). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 566 GoHighLevel MCP Server tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
566 GoHighLevel MCP Server tools catalogued and risk-classified — across an index of 42,500+ MCP servers.