This record as markdown: /tools/ghl/remove-contact-from-workflow.md
What remove_contact_from_workflow does on Ghl
AI agents call remove_contact_from_workflow 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 |
|---|---|---|---|
contactId | string | Yes | Contact ID |
workflowId | string | Yes | Workflow ID |
eventStartTime | string | — | Event start time (ISO format) |
Parameters from the server's own tool schema.
Why remove_contact_from_workflow is rated Critical
Removing a contact from a workflow terminates their automation journey, which cannot be undone without re-adding them and potentially losing progress, trigger history, and timing context. Given GoHighLevel's CRM/marketing automation context, this could disrupt active sales sequences, appointment reminders, or nurture campaigns. Severity is high because misuse could affect many contacts' automated journeys at scale.
From the tool's definition 'Remove contact from a workflow' — removing a contact from a workflow is typically irreversible as the workflow state/progress is lost and re-enrollment may not restore prior state
Attacks that exploit this kind of access
The rule that runs remove_contact_from_workflow 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 remove_contact_from_workflow, this is the rule to start with:
remove_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 Ghl, apply this rule, and every remove_contact_from_workflow call is checked against it from then on.
Questions about remove_contact_from_workflow
Remove contact from a workflow. 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.
remove_contact_from_workflow accepts 3 parameters: contactId, workflowId, eventStartTime. Required: contactId, workflowId. 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 remove_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 Ghl. Nothing to install.
remove_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 remove_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 remove_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.
remove_contact_from_workflow 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