High Risk →

add_contact_to_workflow

Add contact to a workflow

How to control add_contact_to_workflow ↓

AI agents invoke add_contact_to_workflow to trigger actions in GoHighLevel MCP Server. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.

High Risk

Adding a contact to a workflow initiates automated processes (messaging, follow-ups, sequences) that can have wide-reaching external effects such as sending emails/SMS, updating records, or triggering further automations. This is an Execute-level action because it triggers external operations whose effects depend on the workflow configuration, which may be irreversible in practice.

From the tool's definition 'Add contact to a workflow' — triggers automated workflow execution for a contact

Documented attack patterns abuse exactly the kind of access add_contact_to_workflow gives an agent:

PolicyLayer is an MCP gateway — it sits between your AI agents and GoHighLevel MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for add_contact_to_workflow:

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "add_contact_to_workflow": {
      "limits": [
        {
          "counter": "add_contact_to_workflow_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

add_contact_to_workflow stays usable, but rate-capped — a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.

  1. Create a free account and register GoHighLevel MCP Server — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
RATE-LIMIT THIS TOOL →

Free to start. No card required.

Go deeper

What does the add_contact_to_workflow tool do? +

Add contact to a workflow. It is categorised as a Execute tool in the GoHighLevel MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on add_contact_to_workflow? +

Register the GoHighLevel MCP Server MCP server in PolicyLayer and add a rule for add_contact_to_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 add_contact_to_workflow? +

add_contact_to_workflow is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit add_contact_to_workflow? +

Yes. Add a rate_limit block to the add_contact_to_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 add_contact_to_workflow completely? +

Set action: deny in the PolicyLayer policy for add_contact_to_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 add_contact_to_workflow? +

add_contact_to_workflow is provided by the GoHighLevel MCP Server MCP server (busybee3333/go-high-level-mcp-2026-complete). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every GoHighLevel MCP Server tool call.

Deterministic rules across all 566 GoHighLevel MCP Server tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

Free to start. No card required.

566 GoHighLevel MCP Server tools catalogued and risk-classified — across an index of 42,500+ MCP servers.

// GET IN TOUCH

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

Message sent.

We'll get back to you soon.