Delete a product by ID
AI agents call ghl_delete_product 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.
The tool permanently removes a product from the system with no undo capability. In a CRM/business automation context, deleting products can disrupt sales pipelines, reporting, and inventory management. While not as critical as financial transactions, the irreversible nature and potential business impact justify 'Destructive' classification over 'Write'.
From the tool's definition Tool name contains 'delete' and description states 'Delete a product by ID' — this is an irreversible deletion operation.
Attacks that exploit this kind of access
Delete a product by ID. 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 ghl_delete_product: 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.
ghl_delete_product 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 ghl_delete_product 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 ghl_delete_product. 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.
ghl_delete_product is provided by the GoHighLevel MCP Server MCP server (thinkbedo/gohighlevel_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 →