This record as markdown: /tools/ghl/delete-email-template.md
What delete_email_template does on Ghl
AI agents call delete_email_template 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 |
|---|---|---|---|
templateId | string | Yes | The ID of the template to delete. |
Parameters from the server's own tool schema.
Why delete_email_template is rated Critical
This tool permanently removes an email template, which cannot be undone. Deletion of data is irreversible and falls into the Destructive category. The severity is high because loss of email templates could disrupt marketing campaigns and communications that depend on them, though the blast radius is somewhat limited to templates rather than customer data or financial systems.
From the tool's definition Tool name contains 'delete' and description states 'Delete an email template from GoHighLevel.' The verb 'delete' indicates irreversible removal of data.
Attacks that exploit this kind of access
The rule that runs delete_email_template 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 delete_email_template, this is the rule to start with:
delete_email_template 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 delete_email_template call is checked against it from then on.
Questions about delete_email_template
Delete an email template from GoHighLevel. 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.
delete_email_template accepts 1 parameter: templateId. Required: templateId. 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 delete_email_template: 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.
delete_email_template 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 delete_email_template 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 delete_email_template. 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.
delete_email_template 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