conversations_live_chat_agent_typing
Agent/Ai-Bot is typing a message indicator for live chat
This record as markdown: /tools/aiwerk-mcp-server-ghl/conversations-live-chat-agent-typing.md
What conversations_live_chat_agent_typing does on Ghl
AI agents call conversations_live_chat_agent_typing to retrieve information from Ghl without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
isTyping | string | Yes | Typing status |
visitorId | string | Yes | visitorId is the Unique ID assigned to each Live chat visitor. visitorId will be added soon in <a href="https://highlevel.stoplight.io/docs/integrations/00c5ff2 |
locationId | string | — | Location Id Defaults to GHL_LOCATION_ID when omitted. |
conversationId | string | Yes | Conversation Id |
Parameters from the server's own tool schema.
Why conversations_live_chat_agent_typing is rated Low
Even though conversations_live_chat_agent_typing only reads data, uncontrolled read access leaks sensitive information and racks up API costs: an agent caught in a retry loop can make thousands of calls a minute without anyone noticing.
Attacks that exploit this kind of access
The rule that runs conversations_live_chat_agent_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 conversations_live_chat_agent_typing, this is the rule to start with:
conversations_live_chat_agent_typing is read-only, so it stays allowed. 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 conversations_live_chat_agent_typing call is checked against it from then on.
Questions about conversations_live_chat_agent_typing
Agent/Ai-Bot is typing a message indicator for live chat. It is categorised as a Read tool in the Ghl MCP Server, which means it retrieves data without modifying state.
conversations_live_chat_agent_typing accepts 4 parameters: isTyping, visitorId, locationId, 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 conversations_live_chat_agent_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.
conversations_live_chat_agent_typing is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the conversations_live_chat_agent_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 conversations_live_chat_agent_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.
conversations_live_chat_agent_typing is provided by the Ghl MCP server (@aiwerk/mcp-server-ghl). 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