tmux_adopt_session
Adopt an existing tmux PANE as a Yaver task. The session continues running and the pane's output is streamed as task output. Useful for bringing pre-existing agent sessions under Yaver management. One session split across several panes is several agents and therefore several tasks — pass pane to ...
This record as markdown: /tools/io-github-kivanccakmak-yaver/tmux-adopt-session.md
What tmux_adopt_session does on Yaver
AI agents invoke tmux_adopt_session 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 |
|---|---|---|---|
pane | string | — | tmux pane id to adopt, e.g. "%37" (from tmux_list_sessions). Omit to adopt the session's active pane. |
session_name | string | Yes | Name of the tmux session to adopt |
Parameters from the server's own tool schema.
Why tmux_adopt_session is rated High
Brings running shell sessions under management, enabling execution control over existing processes.
From the tool's definition Adopt existing tmux PANE, session continues running, streamed as task output
Attacks that exploit this kind of access
The rule that runs tmux_adopt_session 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 tmux_adopt_session, this is the rule to start with:
tmux_adopt_session 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 tmux_adopt_session call is checked against it from then on.
Questions about tmux_adopt_session
Adopt an existing tmux PANE as a Yaver task. The session continues running and the pane's output is streamed as task output. Useful for bringing pre-existing agent sessions under Yaver management. One session split across several panes is several agents and therefore several tasks — pass pane to pick which one; without it the session's currently-active pane is adopted, which on a split window may not be the agent you meant. 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.
tmux_adopt_session accepts 2 parameters: pane, session_name. Required: session_name. 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 tmux_adopt_session: 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.
tmux_adopt_session 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 tmux_adopt_session 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 tmux_adopt_session. 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.
tmux_adopt_session 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