update_conversation
Update conversation properties (star, mark read, etc.)
This record as markdown: /tools/hridayshah7-gohighlevel-mcp/update-conversation.md
What update_conversation does on GoHighLevel MCP Server
AI agents use update_conversation 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_conversation is rated Medium
The tool modifies conversation metadata (star status, read status) but does not delete data or trigger external operations. These changes are reversible, placing it in the Write category. Severity is medium because a compromised agent could modify conversation states across the CRM system, potentially hiding important messages or conversations, but the changes are not permanent and can be undone.
From the tool's definition Tool name is 'update_conversation' and description states it updates conversation properties like 'star, mark read, etc.' - these are reversible modifications to existing conversation state.
Attacks that exploit this kind of access
The rule that runs update_conversation 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_conversation, this is the rule to start with:
update_conversation 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_conversation call is checked against it from then on.
Questions about update_conversation
Update conversation properties (star, mark read, etc.). 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_conversation: 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_conversation 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_conversation 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_conversation. 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_conversation 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.
More on GoHighLevel MCP Server, and thousands of servers like it.
This server
Across the catalogue