yaver_request_render
Signal that visible UI changes are ready to render. This is advisory: by default Yaver shows a Render updates action, and auto-render runs only when the user explicitly enabled it and the coding turn is safe. Call once after completing a visible UI change; do not call for backend/docs-only work o...
This record as markdown: /tools/io-github-kivanccakmak-yaver/yaver-request-render.md
What yaver_request_render does on Yaver
AI agents invoke yaver_request_render to trigger actions in Yaver. 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 |
|---|---|---|---|
reason | string | Yes | Why one render is warranted. |
summary | string | — | Short user-facing description of what is ready to inspect. |
Parameters from the server's own tool schema.
Why yaver_request_render is rated High
Triggers an external rendering operation on the mobile device, causing UI state changes.
From the tool's definition Signal that visible UI changes are ready to render
Attacks that exploit this kind of access
The rule that runs yaver_request_render 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 yaver_request_render, this is the rule to start with:
yaver_request_render 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 Yaver, apply this rule, and every yaver_request_render call is checked against it from then on.
Questions about yaver_request_render
Signal that visible UI changes are ready to render. This is advisory: by default Yaver shows a Render updates action, and auto-render runs only when the user explicitly enabled it and the coding turn is safe. Call once after completing a visible UI change; do not call for backend/docs-only work or merely because a task completed. Requires YAVER_TASK_ID. It is categorised as a Execute tool in the Yaver MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
yaver_request_render accepts 2 parameters: reason, summary. Required: reason. 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 yaver_request_render: 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.
yaver_request_render 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 yaver_request_render 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 yaver_request_render. 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.
yaver_request_render 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.
Across the catalogue