This record as markdown: /tools/ghl/send-sms.md
What send_sms does on Ghl
AI agents use send_sms 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 |
|---|---|---|---|
message | string | Yes | The SMS message content to send |
contactId | string | Yes | The unique ID of the contact to send SMS to |
fromNumber | string | — | Optional: Phone number to send from (must be configured in GHL) |
Parameters from the server's own tool schema.
Why send_sms is rated Medium
Sending an SMS is a Write operation: it creates a new message record and triggers an outbound communication. While the message delivery itself is irreversible at the recipient end, the classification is Write rather than Destructive because the tool does not delete or overwrite data in the system.
From the tool's definition Tool description states 'Send an SMS message to a contact' — this creates/modifies communication records by dispatching a message.
Attacks that exploit this kind of access
The rule that runs send_sms 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_sms, this is the rule to start with:
send_sms 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_sms call is checked against it from then on.
Questions about send_sms
Send an SMS 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_sms accepts 3 parameters: message, contactId, fromNumber. Required: message, 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_sms: 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_sms 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_sms 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_sms. 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_sms 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