chat_reply
Send an owner-side reply to a visitor. Shows up live in the browser widget via SSE.
This record as markdown: /tools/io-github-kivanccakmak-yaver/chat-reply.md
What chat_reply does on Yaver
AI agents use chat_reply to create or update resources in Yaver, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Yaver environment.
| Parameter | Type | Required | Description |
|---|---|---|---|
vid | string | Yes | |
text | string | Yes |
Parameters from the server's own tool schema.
Why chat_reply is rated Medium
This tool creates and delivers new messages to a visitor interface in real-time. While it doesn't delete data (Destructive), execute arbitrary code (Execute), move money (Financial), or merely read (Read), it does reversibly create/modify communication records.
From the tool's definition Tool description states 'Send an owner-side reply to a visitor' — a create/send operation that modifies communication state in the browser widget. The description explicitly indicates this writes data that 'shows up live', confirming it has side effects.
Attacks that exploit this kind of access
The rule that runs chat_reply 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_reply, this is the rule to start with:
chat_reply stays usable, but capped: an agent stuck in a loop can't make hundreds of changes a minute. 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_reply call is checked against it from then on.
Questions about chat_reply
Send an owner-side reply to a visitor. Shows up live in the browser widget via SSE. It is categorised as a Write tool in the Yaver MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
chat_reply accepts 2 parameters: vid, text. Required: vid, text. 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_reply: 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_reply is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the chat_reply 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_reply. 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_reply 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