Cancel a scheduled campaign message for a contact
AI agents call cancel_scheduled_campaign_message 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.
Cancelling a scheduled campaign message cannot be undone; once cancelled, that specific scheduled send is permanently removed. While it doesn't delete data records, it irreversibly aborts a pending operation. Severity is medium because it affects outbound messaging for a single contact rather than bulk data or financial records.
From the tool's definition 'Cancel a scheduled campaign message' - cancelling a scheduled message is an irreversible action that permanently removes the pending delivery of that message
Documented attack patterns abuse exactly the kind of access cancel_scheduled_campaign_message 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 cancel_scheduled_campaign_message:
{
"version": "1",
"default": "deny",
"hide": [
"cancel_scheduled_campaign_message"
]
} cancel_scheduled_campaign_message 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.
Cancel a scheduled campaign message for a contact. 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 cancel_scheduled_campaign_message: 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.
cancel_scheduled_campaign_message 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 cancel_scheduled_campaign_message 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 cancel_scheduled_campaign_message. 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.
cancel_scheduled_campaign_message 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.