dogfood_status
Report whether Yaver itself is currently running in contributor Dogfood mode or Production mode. Returns the active Yaver checkout and live attach-session state. Pass device_id when the Dogfood renderer is a remote Yaver machine. Call this before interpreting 'reload', 're-render', or 'refresh Ya...
This record as markdown: /tools/io-github-kivanccakmak-yaver/dogfood-status.md
What dogfood_status does on Yaver
AI agents call dogfood_status 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 |
|---|---|---|---|
device_id | string | — | Optional owned remote Yaver machine running the Dogfood browser lane. Empty means this machine. |
Parameters from the server's own tool schema.
Why dogfood_status is rated Low
Retrieves status information about Yaver's runtime mode with no side effects or system modifications.
From the tool's definition Report whether Yaver itself is currently running, returns active Yaver checkout and attach-session state.
Attacks that exploit this kind of access
The rule that runs dogfood_status 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_status, this is the rule to start with:
dogfood_status 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 dogfood_status call is checked against it from then on.
Questions about dogfood_status
Report whether Yaver itself is currently running in contributor Dogfood mode or Production mode. Returns the active Yaver checkout and live attach-session state. Pass device_id when the Dogfood renderer is a remote Yaver machine. Call this before interpreting 'reload', 're-render', or 'refresh Yaver': when active, use dogfood_rerender rather than a Hermes or unrelated project reload. It is categorised as a Read tool in the Yaver MCP Server, which means it retrieves data without modifying state.
dogfood_status 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_status: 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_status 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 dogfood_status 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_status. 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_status 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