dogfood_rerender
Re-render Yaver itself through the active contributor Dogfood Expo browser lane. Fails explicitly when Dogfood is inactive or its browser lane is not serving; never falls through to Hermes or reloads another project. Pass device_id for the remote primary/render machine. Use when the user says rel...
This record as markdown: /tools/io-github-kivanccakmak-yaver/dogfood-rerender.md
What dogfood_rerender does on Yaver
AI agents invoke dogfood_rerender 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 |
|---|---|---|---|
device_id | string | — | Optional owned remote Yaver machine running Dogfood. Empty means this machine. |
Parameters from the server's own tool schema.
Why dogfood_rerender is rated High
Triggers an external re-render/reload operation on a running Expo browser lane.
From the tool's definition Re-render Yaver itself through the active contributor Dogfood Expo browser lane
Attacks that exploit this kind of access
The rule that runs dogfood_rerender 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 dogfood_rerender, this is the rule to start with:
dogfood_rerender 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 dogfood_rerender call is checked against it from then on.
Questions about dogfood_rerender
Re-render Yaver itself through the active contributor Dogfood Expo browser lane. Fails explicitly when Dogfood is inactive or its browser lane is not serving; never falls through to Hermes or reloads another project. Pass device_id for the remote primary/render machine. Use when the user says reload/re-render/refresh Yaver and dogfood_status reports active. 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.
dogfood_rerender accepts 1 parameter: device_id. 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 dogfood_rerender: 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.
dogfood_rerender 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 dogfood_rerender 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 dogfood_rerender. 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.
dogfood_rerender 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