update_message_status

Update the delivery status of a message

SERVERGhl SOURCEghl-mcp-server

Medium RISK CLASS

Category Write

Parameters 52 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/ghl/update-message-status.md

WHAT IT DOES

What update_message_status does on Ghl

AI agents use update_message_status to create or update resources in Ghl, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Ghl environment.

Parameter	Type	Required	Description
`error`	object	—	Error details if status is failed
`status`	string	Yes	New status for the message
`messageId`	string	Yes	The unique ID of the message to update
`recipients`	array	—	Email delivery status for additional recipients
`emailMessageId`	string	—	Email message ID if updating email status

Parameters from the server's own tool schema.

RISK

Why update_message_status is rated Medium

This tool updates message metadata (delivery status) rather than creating new data or deleting it. The operation is reversible - status can be changed again. While it modifies data, it lacks the irreversible destructiveness of delete operations and the external execution risk of Execute category tools.

From the tool's definition Tool description states 'Update the delivery status of a message' - this modifies the state of an existing message record reversibly.

Risk signalsAccepts freeform code/query input (error.code)

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs update_message_status safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Ghl, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For update_message_status, this is the rule to start with:

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.

The button opens the PolicyLayer dashboard: create your workspace, connect Ghl, apply this rule, and every update_message_status call is checked against it from then on.

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 Ghl MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

What parameters does update_message_status accept? +

update_message_status accepts 5 parameters: error, status, messageId, recipients, emailMessageId. Required: status, messageId. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on update_message_status? +

Register the Ghl 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 Ghl. 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 Ghl MCP server (ghl-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Ghl, and thousands of servers like it.

This server

All 253 Ghl tools →

Across the catalogue

aroflo_create_or_update_record on AroFlo MCP →team_manager_update_budget on Team Manager MCP → The MCP Attack Database →

Guides

Govern customer-ops agents →Argument validation →Scoped token →