runner_detach
Detach the terminal AND flip the session into autorun mode (default). Pass autorun=false to leave the session dormant.
This record as markdown: /tools/io-github-kivanccakmak-yaver/runner-detach.md
What runner_detach does on Yaver
AI agents invoke runner_detach 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 |
|---|---|---|---|
autorun | boolean | — | Default true — after detach, the keeper drains the queue. |
sessionName | string | Yes |
Parameters from the server's own tool schema.
Why runner_detach is rated High
This tool modifies session execution state by enabling autorun mode, which causes commands/processes to run automatically without further user interaction. 'Autorun mode' means the session will execute operations autonomously, making this an Execute-category tool with high severity since an AI agent misusing it could trigger uncontrolled autonomous execution of arbitrary operations in the session.
From the tool's definition Detach the terminal AND flip the session into autorun mode (default)
Attacks that exploit this kind of access
The rule that runs runner_detach 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_detach, this is the rule to start with:
runner_detach 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_detach call is checked against it from then on.
Questions about runner_detach
Detach the terminal AND flip the session into autorun mode (default). Pass autorun=false to leave the session dormant. 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_detach accepts 2 parameters: autorun, sessionName. Required: 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_detach: 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_detach 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_detach 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_detach. 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_detach 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