runner_autorun
Force a session's keeper mode to on|off explicitly (bypasses attach/detach).
This record as markdown: /tools/io-github-kivanccakmak-yaver/runner-autorun.md
What runner_autorun does on Yaver
AI agents invoke runner_autorun 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 |
|---|---|---|---|
mode | string | Yes | on|off |
sessionName | string | Yes |
Parameters from the server's own tool schema.
Why runner_autorun is rated High
This tool forcibly controls session keeper mode, bypassing normal attach/detach mechanisms. It triggers an external operational state change on a running session, which qualifies as Execute. The ability to bypass normal attach/detach controls and force session states could disrupt running processes or enable unintended execution contexts, giving it high severity.
From the tool's definition Force a session's keeper mode to on|off explicitly (bypasses attach/detach)
Attacks that exploit this kind of access
The rule that runs runner_autorun 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_autorun, this is the rule to start with:
runner_autorun 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 runner_autorun call is checked against it from then on.
Questions about runner_autorun
Force a session's keeper mode to on|off explicitly (bypasses attach/detach). 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.
runner_autorun accepts 2 parameters: mode, sessionName. Required: mode, 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_autorun: 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_autorun 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 runner_autorun 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_autorun. 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_autorun 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