cancel-scheduled-message
Post the messageId for the API to delete a scheduled message. <br />
This record as markdown: /tools/drausal-gohighlevel-mcp/cancel-scheduled-message.md
What cancel-scheduled-message does on GoHighLevel MCP Server
AI agents call cancel-scheduled-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-message is rated Critical
Deleting a scheduled message is an irreversible action that cannot be undone. Once canceled, the message is removed from the schedule and cannot be recovered. This meets the Destructive category definition: 'irreversibly deletes or overwrites data, or actions that cannot be undone.' Severity is high because canceling messages could disrupt business communications, affect customer outreach campaigns, or cause missed…
From the tool's definition Tool description states 'delete a scheduled message' - the verb 'delete' is explicitly destructive. The operation removes a scheduled message irreversibly by messageId.
Attacks that exploit this kind of access
The rule that runs cancel-scheduled-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-message, this is the rule to start with:
cancel-scheduled-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-message call is checked against it from then on.
Questions about cancel-scheduled-message
Post the messageId for the API to delete a scheduled message. <br />. 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-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-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-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-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-message is provided by the GoHighLevel MCP Server MCP server (drausal/gohighlevel-mcp). 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