Remove contact from all campaigns
AI agents call remove_contact_from_all_campaigns 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.
Removing a contact from all campaigns is effectively irreversible in practice - it would be difficult to know which campaigns the contact was previously enrolled in, making restoration complex. The 'all campaigns' scope makes the blast radius high, as a single misuse could simultaneously remove a contact from every active marketing campaign they were part of, disrupting all ongoing marketing workflows.
From the tool's definition 'Remove contact from all campaigns' - removes from ALL campaigns simultaneously, which is a broad irreversible bulk action
Documented attack patterns abuse exactly the kind of access remove_contact_from_all_campaigns 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_all_campaigns:
{
"version": "1",
"default": "deny",
"hide": [
"remove_contact_from_all_campaigns"
]
} remove_contact_from_all_campaigns disappears from the agent's tool list entirely, and any attempt to call it is denied. The rest of the server keeps working.
Free to start. No card required.
Remove contact from all campaigns. 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.
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.
remove_contact_from_all_campaigns is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
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.
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.
remove_contact_from_all_campaigns 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.
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.