This record as markdown: /tools/ghl/send-email.md
What send_email does on Ghl
AI agents use send_email 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 | — | HTML email content (optional, takes precedence over message) |
emailCc | array | — | Optional: Array of CC email addresses |
message | string | — | Plain text email content |
subject | string | Yes | Email subject line |
emailBcc | array | — | Optional: Array of BCC email addresses |
contactId | string | Yes | The unique ID of the contact to send email to |
emailFrom | string | — | Optional: Email address to send from (must be configured in GHL) |
attachments | array | — | Optional: Array of attachment URLs |
Parameters from the server's own tool schema.
Why send_email is rated Medium
This tool creates and sends a communication artifact, which is a data modification action. It is not a read operation (it actively sends, not merely retrieves), not destructive (the email itself persists and can be archived rather than permanently deleted), and not financial (no monetary transaction). It is Write because it creates a new message in the system.
From the tool's definition Tool description states 'Send an email message to a contact in GoHighLevel' — this creates a new email message artifact in the system and delivers it to a recipient.
Risk signalsAccepts raw HTML/template content (html)
Attacks that exploit this kind of access
The rule that runs send_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 send_email, this is the rule to start with:
send_email 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 send_email call is checked against it from then on.
Questions about send_email
Send an email message to a contact 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.
send_email accepts 8 parameters: html, emailCc, message, subject, emailBcc, contactId, emailFrom, attachments. Required: subject, contactId. 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 send_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.
send_email 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 send_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 send_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.
send_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.
This server
Across the catalogue