This record as markdown: /tools/ghl/cancel-scheduled-message.md
What cancel_scheduled_message does on Ghl
AI agents call cancel_scheduled_message to permanently remove resources in Ghl, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
| Parameter | Type | Required | Description |
|---|---|---|---|
messageId | string | Yes | The unique ID of the scheduled message to cancel |
Parameters from the server's own tool schema.
Why cancel_scheduled_message is rated Critical
Cancelling a scheduled message destroys the pending send action irreversibly. Unlike a write/update (which modifies data reversibly), cancellation permanently removes the scheduled message from the queue with no recovery path, making it Destructive. Severity is medium because it affects a single scheduled message rather than bulk data.
From the tool's definition 'Cancel a scheduled message before it is sent' — cancelling a scheduled message is an irreversible action that permanently removes the scheduled send, which cannot be undone once cancelled
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 Ghl, 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 Ghl, apply this rule, and every cancel_scheduled_message call is checked against it from then on.
Questions about cancel_scheduled_message
Cancel a scheduled message before it is sent. It is categorised as a Destructive tool in the Ghl MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
cancel_scheduled_message accepts 1 parameter: messageId. Required: messageId. The full parameter table on this page comes from the server's own tool schema.
Register the Ghl 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 Ghl. 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 Ghl MCP server (ghl-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Ghl, and thousands of servers like it.
Across the catalogue