remove_contact_from_workflow · GoHighLevel MCP Server MCP

WHAT IT DOES

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 IT NEEDS A POLICY

Why remove_contact_from_workflow needs a policy

Removing a contact from a workflow modifies a CRM relationship/enrollment state. While it stops future workflow actions for that contact, it is generally reversible by re-adding the contact (as the sibling tool 'add_contact_to_workflow' exists). This is a Write operation rather than Destructive. Misuse could disrupt automated marketing or sales sequences for contacts, giving it medium severity.

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

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

remove_contact_from_workflow Rate-limited

remove_contact_from_workflow stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "remove_contact_from_workflow": {
      "limits": [
        {
          "counter": "remove_contact_from_workflow_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches GoHighLevel MCP Server, so you can run agents against it safely.

FAQ

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 (tailormadeweddings/gohighlevel-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.