send_sms

Send an SMS message to a contact in GoHighLevel

SERVERGoHighLevel MCP Server SOURCEhridayshah7/gohighlevel-mcp

High RISK CLASS

Category Execute

Parameters 00 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/hridayshah7-gohighlevel-mcp/send-sms.md

WHAT IT DOES

What send_sms does on GoHighLevel MCP Server

AI agents invoke send_sms to trigger actions in GoHighLevel MCP Server. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call: builds kicked off, notifications sent, workflows started.

RISK

Why send_sms is rated High

Sending an SMS is an external operation that delivers a message to a real contact outside the system. It is not merely writing data internally; it triggers an irreversible outbound action (the message is delivered and cannot be recalled). This places it in Execute rather than Write, with high severity since a misused tool could spam or harass contacts at scale.

From the tool's definition "Send an SMS message to a contact" — actively triggers external communication to a real person

Attacks that exploit this kind of access

RECOMMENDED RULE

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 Rate-limited

send_sms stays usable, but rate-capped: a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "send_sms": {
      "limits": [
        {
          "counter": "send_sms_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL → Instant setup, no code required.

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.

FAQ

Questions about send_sms

What does the send_sms tool do? +

Send an SMS message to a contact in GoHighLevel. It is categorised as a Execute tool in the GoHighLevel MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on send_sms? +

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.

What risk level is send_sms? +

send_sms is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit send_sms? +

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.

How do I block send_sms completely? +

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.

What MCP server provides send_sms? +

send_sms is provided by the GoHighLevel MCP Server MCP server (hridayshah7/gohighlevel-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on GoHighLevel MCP Server, and thousands of servers like it.

This server

All 255 GoHighLevel MCP Server tools → High-risk tools on this server →

Across the catalogue

send_key_to_window on Frida Game Hacking MCP → All high-risk MCP tools → The MCP Attack Database →

Guides

Govern code and CI agents →Agent sandbox →Least privilege for MCP →