session_transfer

SERVERYaver SOURCEyaver-cli

High RISK CLASS

Category Execute

Parameters 42 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/io-github-kivanccakmak-yaver/session-transfer.md

WHAT IT DOES

What session_transfer does on Yaver

AI agents invoke session_transfer 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
`task_id`	string	Yes	The task ID of the session to transfer
`target_device`	string	Yes	Target device ID or hostname prefix (from your registered devices)
`workspace_mode`	string	—	How to transfer workspace: 'none', 'git', or 'tar'. Default: 'git'.
`include_workspace`	boolean	—	Include workspace files (default: false)

Parameters from the server's own tool schema.

RISK

Why session_transfer is rated High

This tool triggers an external multi-step operation: it packages session state (conversation history, agent state, optionally workspace), transmits it to another device, and imports it there. This is not a simple read or write — it executes a cross-device transfer operation whose effects depend on arguments (target device, session scope).

From the tool's definition Transfer an AI agent session from THIS machine to another device in one step... packaged, sent to the target device, and imported there

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs session_transfer 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 session_transfer, this is the rule to start with:

session_transfer Rate-limited

session_transfer 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.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "session_transfer": {
      "limits": [
        {
          "counter": "session_transfer_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Yaver, apply this rule, and every session_transfer call is checked against it from then on.

FAQ

Questions about session_transfer

What does the session_transfer tool do? +

Transfer an AI agent session from THIS machine to another device in one step. The session (conversation history, agent state, optionally workspace) is packaged, sent to the target device, and imported there. The user can then continue working from the target device via mobile or desktop. Supports Claude Code, Aider, Codex, Goose, Amp, OpenCode sessions. 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.

What parameters does session_transfer accept? +

session_transfer accepts 4 parameters: task_id, target_device, workspace_mode, include_workspace. Required: task_id, target_device. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on session_transfer? +

Register the Yaver MCP server in PolicyLayer and add a rule for session_transfer: 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.

What risk level is session_transfer? +

session_transfer is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit session_transfer? +

Yes. Add a rate_limit block to the session_transfer 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.

How do I block session_transfer completely? +

Set action: deny in the PolicyLayer policy for session_transfer. 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.

What MCP server provides session_transfer? +

session_transfer 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.

KEEP EXPLORING

More on Yaver, and thousands of servers like it.

This server

All 645 Yaver tools → High-risk tools on this server →

Across the catalogue

All high-risk MCP tools → The MCP Attack Database →

Guides

Govern code and CI agents →Agent sandbox →Least privilege for MCP →