emails_update_template

Update a template

SERVERGhl SOURCE@aiwerk/mcp-server-ghl

Medium RISK CLASS

Category Write

Parameters 85 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/aiwerk-mcp-server-ghl/emails-update-template.md

WHAT IT DOES

What emails_update_template does on Ghl

AI agents use emails_update_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
`dnd`	object	Yes
`html`	string	Yes
`updatedBy`	string	Yes
`editorType`	string	Yes
`locationId`	string	—	Defaults to GHL_LOCATION_ID when omitted.
`templateId`	string	Yes
`isPlainText`	boolean	—
`previewText`	string	—

Parameters from the server's own tool schema.

RISK

Why emails_update_template is rated Medium

An AI agent can call emails_update_template faster than any human can review: one bad instruction and it creates or modifies resources in Ghl by the hundred, each call as confident as the last.

Risk signalsAccepts raw HTML/template content (html) · High parameter count (11 properties)

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs emails_update_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 emails_update_template, this is the rule to start with:

emails_update_template Rate-limited

emails_update_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.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "emails_update_template": {
      "limits": [
        {
          "counter": "emails_update_template_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Ghl, apply this rule, and every emails_update_template call is checked against it from then on.

FAQ

Questions about emails_update_template

What does the emails_update_template tool do? +

Update a template. 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.

What parameters does emails_update_template accept? +

emails_update_template accepts 8 parameters: dnd, html, updatedBy, editorType, locationId, templateId, isPlainText, previewText. Required: dnd, html, updatedBy, editorType, templateId. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on emails_update_template? +

Register the Ghl MCP server in PolicyLayer and add a rule for emails_update_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.

What risk level is emails_update_template? +

emails_update_template is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit emails_update_template? +

Yes. Add a rate_limit block to the emails_update_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.

How do I block emails_update_template completely? +

Set action: deny in the PolicyLayer policy for emails_update_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.

What MCP server provides emails_update_template? +

emails_update_template is provided by the Ghl MCP server (@aiwerk/mcp-server-ghl). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Ghl, and thousands of servers like it.

This server

All 569 Ghl tools →

Across the catalogue

aroflo_create_or_update_record on AroFlo MCP → The MCP Attack Database →

Guides

Govern customer-ops agents →Argument validation →Scoped token →