Critical Risk →

remove_contact_from_campaign

Remove contact from a specific campaign

How to control remove_contact_from_campaign ↓

AI agents call remove_contact_from_campaign 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.

Critical Risk

Removing a contact from a campaign is a destructive action because it severs the campaign association, stopping any future scheduled messages or automations for that contact. This is typically not easily reversible (the contact would need to be re-added, and any already-skipped sends are lost). The blast radius is medium — it affects individual contact engagement but does not delete data entirely.

From the tool's definition 'Remove contact from a specific campaign' — the word 'remove' indicates an irreversible disassociation of a contact from a campaign

Documented attack patterns abuse exactly the kind of access remove_contact_from_campaign 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 remove_contact_from_campaign:

policy.json
{
  "version": "1",
  "default": "deny",
  "hide": [
    "remove_contact_from_campaign"
  ]
}

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

  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.
RESTRICT THIS TOOL →

Free to start. No card required.

Go deeper

What does the remove_contact_from_campaign tool do? +

Remove contact from a specific campaign. 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_campaign? +

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

remove_contact_from_campaign 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_campaign? +

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

Set action: deny in the PolicyLayer policy for remove_contact_from_campaign. 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_campaign? +

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

Free to start. No card required.

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