send_sms
Send an SMS message to a contact in GoHighLevel
This record as markdown: /tools/thinkbedo-gohighlevel-mcp/send-sms.md
What send_sms does on GoHighLevel MCP Server
AI agents use send_sms to create or update resources in GoHighLevel MCP Server, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your GoHighLevel MCP Server environment.
Why send_sms is rated Medium
This tool creates new data (outbound SMS messages) with reversible side effects (messages can be deleted or communication logs cleared in most systems). It does not execute arbitrary code, delete data irreversibly, or move money. While it does affect external communication channels, the core operation is data creation/transmission rather than execution of unpredictable operations.
From the tool's definition Tool name 'send_sms' and description 'Send an SMS message to a contact in GoHighLevel' indicate the tool creates/transmits a new message artifact (SMS communication) that modifies contact communication history.
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 GoHighLevel MCP Server, 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 GoHighLevel MCP Server, 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 GoHighLevel MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the GoHighLevel MCP Server 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 GoHighLevel MCP Server. 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 GoHighLevel MCP Server MCP server (thinkbedo/gohighlevel_mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on GoHighLevel MCP Server, and thousands of servers like it.
This server
Across the catalogue