This record as markdown: /tools/aiwerk-mcp-server-ghl/conversations-send-a-new-message.md
What conversations_send_a_new_message does on Ghl
AI agents use conversations_send_a_new_message 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 content of the message |
type | string | Yes | Type of message being sent |
status | string | Yes | Message status |
emailCc | array | — | Array of CC email addresses |
emailTo | string | — | Email address to send to, if different from contact's primary email. This should be a valid email address associated with the contact. |
forward | object | — | Forwarding configuration for emails |
message | string | — | Text content of the message |
subType | object | Yes | Type of message being sent |
subject | string | — | Subject line for email messages |
emailBcc | array | — | Array of BCC email addresses |
threadId | string | — | ID of message thread. For email messages, this is the message ID that contains multiple email messages in the thread |
toNumber | string | — | Recipient phone number for outbound messages |
Parameters from the server's own tool schema.
Why conversations_send_a_new_message is rated Medium
An AI agent can call conversations_send_a_new_message 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 (34 properties)
Attacks that exploit this kind of access
The rule that runs conversations_send_a_new_message 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 conversations_send_a_new_message, this is the rule to start with:
conversations_send_a_new_message 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 conversations_send_a_new_message call is checked against it from then on.
Questions about conversations_send_a_new_message
Send a new message. 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.
conversations_send_a_new_message accepts 12 parameters: html, type, status, emailCc, emailTo, forward, message, subType, subject, emailBcc, threadId, toNumber. Required: type, status, subType. 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 conversations_send_a_new_message: 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.
conversations_send_a_new_message 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 conversations_send_a_new_message 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 conversations_send_a_new_message. 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.
conversations_send_a_new_message 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.
More on Ghl, and thousands of servers like it.
This server
Across the catalogue