live_chat_typing
Send typing indicator for live chat conversations
This record as markdown: /tools/hooker-dev-hailey-mcp/live-chat-typing.md
What live_chat_typing does on GoHighLevel MCP Server
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.
Why live_chat_typing is rated High
This tool triggers an external operation in a live chat system — broadcasting a typing indicator to a conversation. It has a side effect (notifying the other party that someone is typing) but doesn't create or modify persistent data. It's best classified as Execute since it triggers an external real-time event/operation. Severity is low because the blast radius of a misused typing indicator is minimal.
From the tool's definition Send typing indicator for live chat conversations
Attacks that exploit this kind of access
The rule that runs live_chat_typing 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 live_chat_typing, this is the rule to start with:
live_chat_typing stays usable, but rate-capped: a runaway agent can't fire it dozens of times 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 live_chat_typing call is checked against it from then on.
Questions about live_chat_typing
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 (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.
Across the catalogue