add_inbound_message
Manually add an inbound message to a conversation
This record as markdown: /tools/ghl/add-inbound-message.md
What add_inbound_message does on Ghl
AI agents use add_inbound_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 |
|---|---|---|---|
call | object | — | Call details for call-type messages |
date | string | — | Date of the message (ISO format) |
html | string | — | HTML content for email messages |
type | string | Yes | Type of inbound message to add |
altId | string | — | External provider message ID |
emailCc | array | — | CC email addresses |
emailTo | string | — | To email address |
message | string | — | Message content (for text-based messages) |
subject | string | — | Subject line for email messages |
emailBcc | array | — | BCC email addresses |
emailFrom | string | — | From email address |
attachments | array | — | Array of attachment URLs |
Parameters from the server's own tool schema.
Why add_inbound_message is rated Medium
This tool creates new data (an inbound message) in a reversible manner—messages can typically be edited or deleted afterward in most CRM systems. It does not execute arbitrary code, delete data irreversibly, move money, or merely read data.
From the tool's definition Tool description states 'Manually add an inbound message to a conversation', which creates/inserts a new message record in the system. The verb 'add' and action of creating a message entry indicates data modification.
Risk signalsAccepts raw HTML/template content (html) · High parameter count (18 properties)
Attacks that exploit this kind of access
The rule that runs add_inbound_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 add_inbound_message, this is the rule to start with:
add_inbound_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 add_inbound_message call is checked against it from then on.
Questions about add_inbound_message
Manually add an inbound message to a conversation. 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.
add_inbound_message accepts 12 parameters: call, date, html, type, altId, emailCc, emailTo, message, subject, emailBcc, emailFrom, attachments. Required: type. 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 add_inbound_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.
add_inbound_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 add_inbound_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 add_inbound_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.
add_inbound_message 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