cancel_scheduled_campaign_message
Cancel a scheduled campaign message for a contact
This record as markdown: /tools/busybee3333-go-high-level-mcp-2026-complete/cancel-scheduled-campaign-message.md
What cancel_scheduled_campaign_message does on GoHighLevel MCP Server
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.
Why cancel_scheduled_campaign_message is rated Critical
Cancelling a scheduled campaign message permanently removes it from the send queue. Unlike a soft delete or update, cancellation of a scheduled message cannot be reversed — the scheduled send event is destroyed. This fits the Destructive category as the action is irreversible, though the blast radius is medium since it affects a single scheduled message rather than bulk data.
From the tool's definition 'Cancel a scheduled campaign message' — cancelling a scheduled message is an irreversible action that removes a pending communication that cannot be undone once cancelled.
Attacks that exploit this kind of access
The rule that runs cancel_scheduled_campaign_message 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 cancel_scheduled_campaign_message, this is the rule to start with:
cancel_scheduled_campaign_message 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 GoHighLevel MCP Server, apply this rule, and every cancel_scheduled_campaign_message call is checked against it from then on.
Questions about cancel_scheduled_campaign_message
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.
More on GoHighLevel MCP Server, and thousands of servers like it.
Across the catalogue