chat_conversations
List open chat conversations with the visitors from the self-hosted chat widget.
This record as markdown: /tools/io-github-kivanccakmak-yaver/chat-conversations.md
What chat_conversations does on Yaver
AI agents call chat_conversations to retrieve information from Yaver without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why chat_conversations is rated Low
This tool retrieves and queries data about existing chat conversations without modifying, executing external operations, or destroying data. It fits the 'Read' category as a simple data retrieval function. The blast radius of misuse is minimal—an agent would only gain visibility into chat history, which is low severity. No financial, destructive, or executable operations are involved.
From the tool's definition Tool name 'chat_conversations' combined with description 'List open chat conversations' indicates a retrieval operation.
Attacks that exploit this kind of access
The rule that runs chat_conversations safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Yaver, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For chat_conversations, this is the rule to start with:
chat_conversations 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 Yaver, apply this rule, and every chat_conversations call is checked against it from then on.
Questions about chat_conversations
List open chat conversations with the visitors from the self-hosted chat widget. It is categorised as a Read tool in the Yaver MCP Server, which means it retrieves data without modifying state.
Register the Yaver MCP server in PolicyLayer and add a rule for chat_conversations: 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 Yaver. Nothing to install.
chat_conversations 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 chat_conversations 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 chat_conversations. 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.
chat_conversations is provided by the Yaver MCP server (yaver-cli). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Yaver, and thousands of servers like it.
This server
Across the catalogue