This record as markdown: /tools/ghl/live-chat-typing.md
What live_chat_typing does on Ghl
AI agents invoke live_chat_typing to trigger actions in Ghl. 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.
| Parameter | Type | Required | Description |
|---|---|---|---|
isTyping | boolean | Yes | Whether the agent is currently typing |
visitorId | string | Yes | Unique visitor ID for the live chat session |
conversationId | string | Yes | The conversation ID for the live chat |
Parameters from the server's own tool schema.
Why live_chat_typing is rated High
This tool triggers an external operation (sending a typing indicator) in a live chat system. It doesn't read, write persistent data, or delete anything — it sends a transient signal to an external chat platform. The blast radius if misused is minimal, as it only sends a typing indicator that disappears automatically.
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 Ghl, 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 Ghl, 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 Ghl MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
live_chat_typing accepts 3 parameters: isTyping, visitorId, conversationId. Required: isTyping, visitorId, conversationId. The full parameter table on this page comes from the server's own tool schema.
Register the Ghl 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 Ghl. 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 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.
More on Ghl, and thousands of servers like it.
This server
Across the catalogue