schedule_email_campaign_v2
Schedule or start an Email Campaign V2 campaign. The campaign must be in draft, cancelled, or paused status.
This record as markdown: /tools/busybee3333-go-high-level-mcp-2026-complete/schedule-email-campaign-v2.md
What schedule_email_campaign_v2 does on GoHighLevel MCP Server
AI agents use schedule_email_campaign_v2 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 schedule_email_campaign_v2 is rated Medium
This is a Write operation because it modifies campaign state and initiates email communications, which can affect customer engagement and business operations. The severity is high because misconfiguration or unauthorized use could result in sending unwanted bulk communications to many contacts, damaging customer relationships and brand reputation.
From the tool's definition The tool schedules or starts an email campaign, which creates/modifies campaign state (from draft/cancelled/paused to scheduled/active).
Attacks that exploit this kind of access
The rule that runs schedule_email_campaign_v2 safely
PolicyLayer is an MCP gateway: it sits between your AI agents and GoHighLevel MCP Server, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For schedule_email_campaign_v2, this is the rule to start with:
schedule_email_campaign_v2 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 GoHighLevel MCP Server, apply this rule, and every schedule_email_campaign_v2 call is checked against it from then on.
Questions about schedule_email_campaign_v2
Schedule or start an Email Campaign V2 campaign. The campaign must be in draft, cancelled, or paused status. 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.
Register the GoHighLevel MCP Server MCP server in PolicyLayer and add a rule for schedule_email_campaign_v2: 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.
schedule_email_campaign_v2 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 schedule_email_campaign_v2 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 schedule_email_campaign_v2. 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.
schedule_email_campaign_v2 is provided by the GoHighLevel MCP Server MCP server (busybee3333/go-high-level-mcp-2026-complete). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on GoHighLevel MCP Server, and thousands of servers like it.
This server
Across the catalogue