remove_contact_from_workflow

Remove contact from a workflow

SERVERGoHighLevel MCP Server SOURCEhooker-dev/hailey-mcp
Critical RISK CLASS
Category Destructive
Parameters 00 required
Recommended Hiddensee the rule below
Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/hooker-dev-hailey-mcp/remove-contact-from-workflow.md

What remove_contact_from_workflow does on GoHighLevel MCP Server

AI agents call remove_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 remove_contact_from_workflow is rated Critical

Removing a contact from a workflow disrupts ongoing automation sequences. Unlike a soft write operation, workflow removal is typically not reversible in CRM systems — the contact loses their place in the sequence and any pending steps are cancelled. This aligns with Destructive given the irreversible nature of the action and potential business impact (missed follow-ups, lost pipeline progression).

From the tool's definition 'Remove contact from a workflow' — removing a contact from a workflow is an irreversible action that stops automated sequences and cannot easily be undone without re-adding and re-triggering the workflow from the correct step.

Questions about remove_contact_from_workflow

What does the remove_contact_from_workflow tool do? +

Remove contact from a workflow. 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.

How do I enforce a policy on remove_contact_from_workflow? +

Register the GoHighLevel MCP Server 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 GoHighLevel MCP Server. Nothing to install.

What risk level is remove_contact_from_workflow? +

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.

Can I rate-limit remove_contact_from_workflow? +

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.

How do I block remove_contact_from_workflow completely? +

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.

What MCP server provides remove_contact_from_workflow? +

remove_contact_from_workflow is provided by the GoHighLevel MCP Server MCP server (hooker-dev/hailey-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.

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of GoHighLevel MCP Server's. Pull the full record:

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.