update_message_status
Update the delivery status of a message
This record as markdown: /tools/hooker-dev-hailey-mcp/update-message-status.md
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 update_message_status is rated Medium
This tool updates an existing message's delivery status (e.g., pending, delivered, failed), which is a write operation that changes data state. It does not create new messages, delete them, execute arbitrary code, or involve financial transactions. The modification is reversible (status can be changed back).
From the tool's definition Tool name is 'update_message_status' and description states 'Update the delivery status of a message' — this modifies the status attribute of an existing message record, which is a reversible data modification operation.
Attacks that exploit this kind of access
The rule that runs update_message_status 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 update_message_status, this is the rule to start with:
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.
The button opens the PolicyLayer dashboard: create your workspace, connect GoHighLevel MCP Server, apply this rule, and every update_message_status call is checked against it from then on.
Questions about update_message_status
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.
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.
update_message_status 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 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.
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.
update_message_status is provided by the GoHighLevel MCP Server MCP server (hooker-dev/hailey-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on GoHighLevel MCP Server, and thousands of servers like it.
This server
Across the catalogue