update_message_status · GoHighLevel MCP Server MCP

WHAT IT DOES

What update_message_status does on GoHighLevel MCP Server

AI agents use update_message_status 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 update_message_status needs a policy

This tool modifies the status field of an existing message, which is a reversible write operation. While it could mislead users about message delivery if abused (e.g., marking failed messages as delivered), it does not delete data, execute code, move money, or trigger irreversible changes.

From the tool's definition "Update the delivery status of a message" indicates modification of existing message metadata/state without deletion or financial impact.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

update_message_status Rate-limited

update_message_status 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": {
    "update_message_status": {
      "limits": [
        {
          "counter": "update_message_status_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 update_message_status

What does the update_message_status tool do? +

Update the delivery status of a message. 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 update_message_status? +

Register the GoHighLevel MCP Server MCP server in PolicyLayer and add a rule for update_message_status: 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 update_message_status? +

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

Can I rate-limit update_message_status? +

Yes. Add a rate_limit block to the update_message_status 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 update_message_status completely? +

Set action: deny in the PolicyLayer policy for update_message_status. 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 update_message_status? +

update_message_status 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.