update_email_template
Update an existing email template in GoHighLevel.
This record as markdown: /tools/ghl/update-email-template.md
What update_email_template does on Ghl
AI agents use update_email_template to create or update resources in Ghl, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Ghl environment.
| Parameter | Type | Required | Description |
|---|---|---|---|
html | string | Yes | The updated HTML content of the template. |
templateId | string | Yes | The ID of the template to update. |
previewText | string | — | The updated preview text for the template. |
Parameters from the server's own tool schema.
Why update_email_template is rated Medium
This tool creates or modifies data reversibly, which is the definition of Write category. It affects email templates used in GoHighLevel, potentially impacting customer communications at scale, warranting medium severity. Confidence is high because the description explicitly states 'Update' and the reversible nature of template modifications is clear.
From the tool's definition Tool name 'update_email_template' and description 'Update an existing email template' indicate modification of data. The action is reversible—templates can be edited, restored, or reverted to previous versions.
Risk signalsAccepts raw HTML/template content (html)
Attacks that exploit this kind of access
The rule that runs update_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 update_email_template, this is the rule to start with:
update_email_template stays usable, but capped: an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Ghl, apply this rule, and every update_email_template call is checked against it from then on.
Questions about update_email_template
Update an existing email template in GoHighLevel. It is categorised as a Write tool in the Ghl MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
update_email_template accepts 3 parameters: html, templateId, previewText. Required: html, 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 update_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.
update_email_template is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the update_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 update_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.
update_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.
This server
Across the catalogue