delete-contact-from-workflow
A destructive tool on the GoHighLevel MCP server.
This record as markdown: /tools/drausal-gohighlevel-mcp/delete-contact-from-workflow.md
What delete-contact-from-workflow does on GoHighLevel MCP Server
AI agents call delete-contact-from-workflow 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.
Why delete-contact-from-workflow is rated Critical
This tool irreversibly removes a contact from an automated workflow system. While not deleting the contact entirely, it permanently removes their enrollment in a workflow, which is an unrecoverable state change. In a CRM/business automation context, this affects customer journeys and business processes. The 'delete' semantics and irreversible nature of the action classify it as Destructive rather than Write.
From the tool's definition Tool name: 'delete-contact-from-workflow'. Description: 'Delete Contact from Workflow'. The verb 'delete' combined with the action of removing a contact from a workflow indicates an irreversible operation that modifies business-critical state.
Attacks that exploit this kind of access
The rule that runs delete-contact-from-workflow safely
PolicyLayer is an MCP gateway: it sits between your AI agents and GoHighLevel MCP Server, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For delete-contact-from-workflow, this is the rule to start with:
delete-contact-from-workflow 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 GoHighLevel MCP Server, apply this rule, and every delete-contact-from-workflow call is checked against it from then on.
Questions about delete-contact-from-workflow
delete-contact-from-workflow is a destructive tool on the GoHighLevel MCP Server MCP server. 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-contact-from-workflow: 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-contact-from-workflow 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-contact-from-workflow 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-contact-from-workflow. 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-contact-from-workflow is provided by the GoHighLevel MCP Server MCP server (drausal/gohighlevel-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on GoHighLevel MCP Server, and thousands of servers like it.
Across the catalogue