remove_contact_from_workflow

Remove contact from a workflow

SERVERGoHighLevel MCP Server SOURCEhridayshah7/gohighlevel-mcp
Medium RISK CLASS
Category Write
Parameters 00 required
Recommended Rate-limitedsee the rule below
Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/hridayshah7-gohighlevel-mcp/remove-contact-from-workflow.md

What remove_contact_from_workflow does on GoHighLevel MCP Server

AI agents use remove_contact_from_workflow to create or update resources in GoHighLevel MCP Server, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your GoHighLevel MCP Server environment.

Why remove_contact_from_workflow is rated Medium

Removing a contact from a workflow stops future automated actions for that contact, but the contact record itself remains intact. This is a reversible modification (the contact can be re-added to the workflow), making it a Write operation rather than Destructive. Misuse could disrupt marketing automation flows, hence medium severity.

From the tool's definition 'Remove contact from a workflow' — removes an association between a contact and a workflow

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 Write tool in the GoHighLevel MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

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 Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

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 (hridayshah7/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

// 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.