remove_contact_from_workflow

THE RISK

Critical Risk

Removing a contact from a workflow terminates their participation in that automation sequence, potentially losing progress, queued actions, and enrollment state. This is not easily reversible (re-adding may restart the workflow rather than restore state), making it closer to Destructive than Write. Severity is medium as it affects a single contact's workflow enrollment rather than bulk data or financial records.

From the tool's definition 'Remove contact from a workflow' — removing a contact from a workflow is likely irreversible or at least causes loss of automation state/progress that cannot easily be undone

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

HOW TO CONTROL REMOVE_CONTACT_FROM_WORKFLOW

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 remove_contact_from_workflow:

policy.json

{
  "version": "1",
  "default": "deny",
  "hide": [
    "remove_contact_from_workflow"
  ]
}

remove_contact_from_workflow disappears from the agent's tool list entirely, and any attempt to call it is denied. The rest of the server keeps working.

Create a free account and register GoHighLevel MCP Server — nothing to install.
Add this policy — paste it, or build it visually.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

RESTRICT THIS TOOL →

Free to start. No card required.

EXPLORE

More GoHighLevel MCP Server tools

Financial send_invoice Send an invoice to customer Destructive bulk_delete_social_posts Delete multiple social media posts at once (max 50) Destructive cancel_scheduled_email Cancel a scheduled email before it is sent Destructive cancel_scheduled_message Cancel a scheduled message before it is sent Destructive delete_appointment Cancel/delete an appointment from GoHighLevel Destructive delete_appointment_note Delete an appointment note Destructive delete_calendar Delete a calendar from GoHighLevel Destructive delete_calendar_group Delete a calendar group

All 255 GoHighLevel MCP Server tools →

Destructive tools on other servers

Frida Game Hacking MCP clear_scan MegaMemory remove_concept Frida Agent MCP kill_app 1MCP Server mcp_uninstall

Go deeper

Critical-risk tools in GoHighLevel MCP Server → Every critical-risk tool this server exposes, in one view.
All critical-risk MCP tools → Every critical-risk tool across the catalogue, and the policy pattern that contains them.
The MCP Attack Database → Documented attack patterns against MCP deployments — and the policies that stop them.
Rate Limiting MCP Tool Calls: A Practical Guide →
MCP Security: Why Prompt Guardrails Aren't Enough →

FAQ

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 (mastanley13/gohighlevel-mcp). 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 255 GoHighLevel MCP Server tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

GOVERN GOHIGHLEVEL →

Free to start. No card required.

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

// WHAT REMOVE_CONTACT_FROM_WORKFLOW ON GOHIGHLEVEL MCP SERVER DOES

// THE RISK

// HOW TO CONTROL REMOVE_CONTACT_FROM_WORKFLOW

// EXPLORE