This record as markdown: /tools/ghl/add-contact-to-campaign.md
What add_contact_to_campaign does on Ghl
AI agents use add_contact_to_campaign to create or update resources in Ghl, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Ghl environment.
| Parameter | Type | Required | Description |
|---|---|---|---|
contactId | string | Yes | Contact ID |
campaignId | string | Yes | Campaign ID |
Parameters from the server's own tool schema.
Why add_contact_to_campaign is rated Medium
This tool creates a new association or modifies contact records by enrolling them in a marketing campaign. This is a reversible write operation with no permanent deletion or financial transaction. The blast radius is medium because erroneous campaign enrollment could affect marketing outreach, but the action can typically be undone by removing the contact from the campaign.
From the tool's definition Tool name 'add_contact_to_campaign' and description 'Add contact to a marketing campaign' indicate creation/modification of enrollment data linking a contact to a campaign.
Attacks that exploit this kind of access
The rule that runs add_contact_to_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 add_contact_to_campaign, this is the rule to start with:
add_contact_to_campaign 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.
The button opens the PolicyLayer dashboard: create your workspace, connect Ghl, apply this rule, and every add_contact_to_campaign call is checked against it from then on.
Questions about add_contact_to_campaign
Add contact to a marketing campaign. It is categorised as a Write tool in the Ghl MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
add_contact_to_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 add_contact_to_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.
add_contact_to_campaign is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the add_contact_to_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 add_contact_to_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.
add_contact_to_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.
This server
Across the catalogue