session_import
Import a session bundle that was exported from another machine. Creates a new task with the transferred session state. Supports Claude Code, Aider, Codex, Goose, Amp, OpenCode, and custom agents.
This record as markdown: /tools/io-github-kivanccakmak-yaver/session-import.md
What session_import does on Yaver
AI agents use session_import to create or update resources in Yaver, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Yaver environment.
| Parameter | Type | Required | Description |
|---|---|---|---|
work_dir | string | — | Target working directory (default: agent's work dir) |
git_clone | boolean | — | Clone the git repo from the bundle's remote URL (default: false) |
bundle_json | string | Yes | The JSON string of the transfer bundle |
Parameters from the server's own tool schema.
Why session_import is rated Medium
This tool modifies state by importing and creating new task records from external session bundles. This is a Write operation because it creates/modifies data reversibly—the imported session can be deleted or modified afterward. While it accepts external input (session bundles), there is no indication it executes arbitrary code or performs destructive operations.
From the tool's definition The tool description states it "Creates a new task with the transferred session state," which is a reversible data creation operation. The import mechanism loads external session bundles into the system.
Attacks that exploit this kind of access
The rule that runs session_import 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_import, this is the rule to start with:
session_import stays usable, but capped: an agent stuck in a loop can't make hundreds of changes 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 session_import call is checked against it from then on.
Questions about session_import
Import a session bundle that was exported from another machine. Creates a new task with the transferred session state. Supports Claude Code, Aider, Codex, Goose, Amp, OpenCode, and custom agents. It is categorised as a Write tool in the Yaver MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
session_import accepts 3 parameters: work_dir, git_clone, bundle_json. Required: bundle_json. 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 session_import: 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.
session_import is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the session_import 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 session_import. 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.
session_import 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