runner_status
Human-readable status for a named autorun task: phases done/current/remaining, [auto-runner] commits with metadata (phase/machine/alias/work-window/mode), current mode, keeper health, last-activity, ETA, per-runner attribution (claude/codex/opencode/glm) with time + tokens where recorded.
This record as markdown: /tools/io-github-kivanccakmak-yaver/runner-status.md
What runner_status does on Yaver
AI agents call runner_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 |
|---|---|---|---|
task | string | — | e.g. n2n — used to parse the matching progress log. |
machine | string | — | Reserved for remote status. |
sessionName | string | — |
Parameters from the server's own tool schema.
Why runner_status is rated Low
runner_status retrieves and displays status information about an autorun task without creating, modifying, deleting, or executing any operations. It is a pure read/query operation that inspects the state of a running process. No side effects or state changes occur.
From the tool's definition The tool provides 'Human-readable status' and reports on 'phases done/current/remaining', 'current mode', 'keeper health', 'last-activity', 'ETA', and 'per-runner attribution' — all observational queries with no modification or execution of tasks.
Attacks that exploit this kind of access
The rule that runs runner_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 runner_status, this is the rule to start with:
runner_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 runner_status call is checked against it from then on.
Questions about runner_status
Human-readable status for a named autorun task: phases done/current/remaining, [auto-runner] commits with metadata (phase/machine/alias/work-window/mode), current mode, keeper health, last-activity, ETA, per-runner attribution (claude/codex/opencode/glm) with time + tokens where recorded. It is categorised as a Read tool in the Yaver MCP Server, which means it retrieves data without modifying state.
runner_status accepts 3 parameters: task, machine, sessionName. 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 runner_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.
runner_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 runner_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 runner_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.
runner_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