This record as markdown: /tools/ghl/remove-contact-from-campaign.md
What remove_contact_from_campaign does on Ghl
AI agents call remove_contact_from_campaign to permanently remove resources in Ghl, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
| Parameter | Type | Required | Description |
|---|---|---|---|
contactId | string | Yes | Contact ID |
campaignId | string | Yes | Campaign ID |
Parameters from the server's own tool schema.
Why remove_contact_from_campaign is rated Critical
Removing a contact from a campaign typically cannot be undone automatically; the contact loses their place in the campaign sequence and any future scheduled messages. This is analogous to a delete/purge operation on a campaign-contact relationship. Given that campaigns are often time-sensitive marketing sequences, misuse could have significant business impact, warranting a high severity rating.
From the tool's definition 'Remove contact from a specific campaign' — removing a contact from a campaign is an irreversible action that terminates the contact's participation in that campaign sequence
Attacks that exploit this kind of access
The rule that runs remove_contact_from_campaign safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Ghl, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For remove_contact_from_campaign, this is the rule to start with:
remove_contact_from_campaign is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.
The button opens the PolicyLayer dashboard: create your workspace, connect Ghl, apply this rule, and every remove_contact_from_campaign call is checked against it from then on.
Questions about remove_contact_from_campaign
Remove contact from a specific campaign. It is categorised as a Destructive tool in the Ghl MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
remove_contact_from_campaign accepts 2 parameters: contactId, campaignId. Required: contactId, campaignId. The full parameter table on this page comes from the server's own tool schema.
Register the Ghl 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 Ghl. Nothing to install.
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.
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.
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.
remove_contact_from_campaign is provided by the Ghl MCP server (ghl-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Ghl, and thousands of servers like it.
Across the catalogue