Schedule or start an Email Campaign V2 campaign. The campaign must be in draft, cancelled, or paused status.
AI agents invoke schedule_email_campaign_v2 to trigger actions in GoHighLevel MCP Server. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.
This tool triggers the execution of an email campaign, sending emails to potentially large lists of contacts. It is an external operation with real-world effects (mass email delivery) that cannot be easily undone once emails are sent. This makes it Execute category with high severity due to the blast radius of potentially spamming thousands of contacts if misused.
From the tool's definition Schedule or start an Email Campaign V2 campaign
Documented attack patterns abuse exactly the kind of access schedule_email_campaign_v2 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 schedule_email_campaign_v2:
{
"version": "1",
"default": "deny",
"tools": {
"schedule_email_campaign_v2": {
"limits": [
{
"counter": "schedule_email_campaign_v2_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
}schedule_email_campaign_v2 stays usable, but rate-capped — a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Schedule or start an Email Campaign V2 campaign. The campaign must be in draft, cancelled, or paused status. It is categorised as a Execute tool in the GoHighLevel MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
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 Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
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.
Deterministic rules across all 566 GoHighLevel MCP Server tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
566 GoHighLevel MCP Server tools catalogued and risk-classified — across an index of 42,500+ MCP servers.