Delete a GoHighLevel opportunity.
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.
This tool permanently removes an opportunity record from the GoHighLevel CRM system. Deletion is irreversible and cannot be undone, fitting the Destructive category. The severity is high because losing opportunity records could impact sales pipelines, revenue tracking, and business operations, though the blast radius is limited to a single opportunity record rather than a database-wide destructive action.
From the tool's definition Tool name is 'delete_opportunity' and description states 'Delete a GoHighLevel opportunity.' The verb 'delete' indicates irreversible removal of data.
Attacks that exploit this kind of access
Delete a GoHighLevel opportunity. 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.
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 (snack-jpg/ghl-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →