Critical Risk →

cancel_scheduled_email

Cancel a scheduled email before it is sent

How to control cancel_scheduled_email ↓

AI agents call cancel_scheduled_email 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.

Critical Risk

Cancelling a scheduled email is an irreversible action — once cancelled, that scheduled send is gone and cannot be un-cancelled. This is not merely a 'write' update but a permanent removal of a pending operation, making it Destructive. Severity is medium because while the action cannot be undone, it affects a single scheduled email rather than bulk data.

From the tool's definition Cancel a scheduled email before it is sent

Documented attack patterns abuse exactly the kind of access cancel_scheduled_email 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_email:

policy.json
{
  "version": "1",
  "default": "deny",
  "hide": [
    "cancel_scheduled_email"
  ]
}

cancel_scheduled_email disappears from the agent's tool list entirely, and any attempt to call it is denied. The rest of the server keeps working.

  1. Create a free account and register GoHighLevel MCP Server — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
RESTRICT THIS TOOL →

Free to start. No card required.

Go deeper

What does the cancel_scheduled_email tool do? +

Cancel a scheduled email before it is sent. 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.

How do I enforce a policy on cancel_scheduled_email? +

Register the GoHighLevel MCP Server 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 GoHighLevel MCP Server. Nothing to install.

What risk level is cancel_scheduled_email? +

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.

Can I rate-limit cancel_scheduled_email? +

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.

How do I block cancel_scheduled_email completely? +

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.

What MCP server provides cancel_scheduled_email? +

cancel_scheduled_email is provided by the GoHighLevel MCP Server MCP server (mastanley13/gohighlevel-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every GoHighLevel MCP Server tool call.

Deterministic rules across all 255 GoHighLevel MCP Server tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

Free to start. No card required.

255 GoHighLevel MCP Server tools catalogued and risk-classified — across an index of 42,500+ MCP servers.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.