This record as markdown: /tools/ghl/cancel-scheduled-email.md
What cancel_scheduled_email does on Ghl
AI agents call cancel_scheduled_email 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 |
|---|---|---|---|
emailMessageId | string | Yes | The unique ID of the scheduled email to cancel |
Parameters from the server's own tool schema.
Why cancel_scheduled_email is rated Critical
Cancelling a scheduled email is an irreversible action — once cancelled, the scheduled send is permanently removed and cannot be undone. This aligns with the Destructive category as the scheduled action is permanently terminated, not merely modified.
From the tool's definition Cancel a scheduled email before it is sent
Attacks that exploit this kind of access
The rule that runs cancel_scheduled_email 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_email, this is the rule to start with:
cancel_scheduled_email 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_email call is checked against it from then on.
Questions about cancel_scheduled_email
Cancel a scheduled email 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_email accepts 1 parameter: emailMessageId. Required: emailMessageId. 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_email: 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_email 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_email 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_email. 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_email 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