chat_history
Return the full message history for one conversation (by visitor id).
This record as markdown: /tools/io-github-kivanccakmak-yaver/chat-history.md
What chat_history does on Yaver
AI agents call chat_history 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.
| Parameter | Type | Required | Description |
|---|---|---|---|
vid | string | Yes | |
limit | integer | — |
Parameters from the server's own tool schema.
Why chat_history is rated Low
This tool retrieves historical data (chat messages) for a specific conversation. The verb 'return' indicates a query/read operation that does not alter, delete, or execute external actions. The severity is low because exposure of chat history, while potentially sensitive, is a data leakage risk rather than a destructive or high-impact capability.
From the tool's definition Tool description states 'Return the full message history for one conversation (by visitor id)' — a retrieval operation with no modification, deletion, or side effects.
Attacks that exploit this kind of access
The rule that runs chat_history 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_history, this is the rule to start with:
chat_history 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_history call is checked against it from then on.
Questions about chat_history
Return the full message history for one conversation (by visitor id). It is categorised as a Read tool in the Yaver MCP Server, which means it retrieves data without modifying state.
chat_history accepts 2 parameters: vid, limit. Required: vid. The full parameter table on this page comes from the server's own tool schema.
Register the Yaver MCP server in PolicyLayer and add a rule for chat_history: 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_history 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_history 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_history. 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_history 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