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.
This tool creates new data (outbound SMS messages) and has external side effects (actually sends SMS to phone numbers). It is not destructive (messages can be retracted or logs deleted), not financial (no money moves), and not mere reading. The high severity reflects that an agent could spam contacts, damage reputation, or incur SMS costs if misused at scale or to wrong numbers.
From the tool's definition Tool name 'send_sms' and description 'Send an SMS message to a contact in GoHighLevel' indicate the tool creates/sends a message, which is a write operation that modifies state (adds a message record and triggers external communication).
Documented attack patterns abuse exactly the kind of access send_sms gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and GoHighLevel MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for send_sms:
{
"version": "1",
"default": "deny",
"tools": {
"send_sms": {
"limits": [
{
"counter": "send_sms_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}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.
Free to start. No card required.
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 (mastanley13/gohighlevel-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 255 GoHighLevel MCP Server tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
255 GoHighLevel MCP Server tools catalogued and risk-classified — across an index of 42,500+ MCP servers.