remove_contact_from_all_campaigns

WHAT IT DOES

What remove_contact_from_all_campaigns does on GoHighLevel MCP Server

AI agents use remove_contact_from_all_campaigns 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_all_campaigns needs a policy

Removing a contact from all campaigns is a reversible write operation (the contact can be re-added), but the blast radius is high because it simultaneously disconnects the contact from every campaign they're enrolled in, potentially disrupting all active marketing workflows for that contact. It modifies CRM data rather than deleting it permanently, so Write is appropriate over Destructive.

From the tool's definition Remove contact from all campaigns

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

remove_contact_from_all_campaigns Rate-limited

remove_contact_from_all_campaigns 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_all_campaigns": {
      "limits": [
        {
          "counter": "remove_contact_from_all_campaigns_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_all_campaigns

What does the remove_contact_from_all_campaigns tool do? +

Remove contact from all campaigns. 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_all_campaigns? +

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

remove_contact_from_all_campaigns 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_all_campaigns? +

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

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

remove_contact_from_all_campaigns is provided by the GoHighLevel MCP Server MCP server (keshigami/ghl-mcp-workiong). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.