This record as markdown: /tools/ghl/delete-opportunity.md
What delete_opportunity does on Ghl
AI agents call delete_opportunity 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 |
|---|---|---|---|
opportunityId | string | Yes | The unique ID of the opportunity to delete |
Parameters from the server's own tool schema.
Why delete_opportunity is rated Critical
The tool permanently removes an opportunity record from the CRM system. This action cannot be undone and results in data loss. Destructive actions have higher severity than Write (which are reversible) or Execute actions. The high severity reflects the potential business impact of losing sales pipeline data, though it is scoped to individual opportunities rather than bulk operations, preventing a critical rating.
From the tool's definition Tool name 'delete_opportunity' combined with description 'Delete an opportunity from GoHighLevel CRM' explicitly indicates irreversible deletion of data.
Attacks that exploit this kind of access
The rule that runs delete_opportunity 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_opportunity, this is the rule to start with:
delete_opportunity 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_opportunity call is checked against it from then on.
Questions about delete_opportunity
Delete an opportunity from GoHighLevel CRM. 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_opportunity accepts 1 parameter: opportunityId. Required: opportunityId. 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_opportunity: 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_opportunity 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_opportunity 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_opportunity. 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_opportunity 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