Send typing indicator for live chat conversations
AI agents invoke live_chat_typing to trigger actions in GoHighLevel MCP Server. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.
Sending a typing indicator triggers an external operation (notifying the live chat system and recipient that someone is typing) without creating or modifying persistent data. It's an ephemeral real-time signal that has no lasting side effects, but it does execute an action against an external messaging system rather than merely reading data.
From the tool's definition Send typing indicator for live chat conversations
Attacks that exploit this kind of access
Send typing indicator for live chat conversations. It is categorised as a Execute tool in the GoHighLevel MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the GoHighLevel MCP Server MCP server in PolicyLayer and add a rule for live_chat_typing: 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.
live_chat_typing is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the live_chat_typing 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 live_chat_typing. 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.
live_chat_typing 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.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →