add_inbound_message · GoHighLevel MCP Server MCP

WHAT IT DOES

What add_inbound_message does on GoHighLevel MCP Server

AI agents use add_inbound_message 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 IT NEEDS A POLICY

Why add_inbound_message needs a policy

This tool creates a new message entry in a conversation thread, which is a reversible write operation. It does not execute arbitrary code, delete data, or move money. However, it could be misused to inject false messages into customer conversations (e.g., impersonating customer responses), which could mislead agents or trigger automated workflows based on fake customer input.

From the tool's definition Tool name 'add_inbound_message' and description 'Manually add an inbound message to a conversation' indicate creation of a new message record in the CRM system.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

add_inbound_message Rate-limited

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.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "add_inbound_message": {
      "limits": [
        {
          "counter": "add_inbound_message_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches GoHighLevel MCP Server, so you can run agents against it safely.

FAQ

Questions about add_inbound_message

What does the add_inbound_message tool do? +

Manually add an inbound message to a conversation. 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.

How do I enforce a policy on add_inbound_message? +

Register the GoHighLevel MCP Server 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 GoHighLevel MCP Server. Nothing to install.

What risk level is add_inbound_message? +

add_inbound_message is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit add_inbound_message? +

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.

How do I block add_inbound_message completely? +

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.

What MCP server provides add_inbound_message? +

add_inbound_message is provided by the GoHighLevel MCP Server MCP server (mindflowedstudios/mindflowed_mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.