AI agents invoke dev_environment_clone_start 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 |
|---|---|---|---|
repos | array | — | |
dryRun | boolean | — | |
target | object | — | |
verify | boolean | — | |
runnerIds | array | — | |
syncKinds | array | — | |
configKeys | array | — | Optional subset of config keys to clone. |
skipConfigs | boolean | — | Skip allowlisted developer config clone (.vimrc, nvim, tmux, shell rc, i3, terminal, runner configs). |
configureCode | boolean | — | Set the first cloned repo as yaver code repo on target. |
installMissing | boolean | — | Install missing supported tools on target. |
sourceDeviceId | string | — | Optional source Yaver device id; empty means this machine. |
targetDeviceId | string | — | Existing target Yaver device id/name/alias. |
Parameters from the server's own tool schema.
dev_environment_clone_start triggers real processes with real consequences. An agent gone sideways doesn't fire it once — it starts dozens of builds, sends mass notifications, or burns through compute before anyone looks up.
Risk signalsAccepts file system path (repos[].dir) · Accepts URL/endpoint input (repos[].url) · High parameter count (24 properties)
Attacks that exploit this kind of access
Start cloning a coding-focused Yaver dev environment. Reuses toolchain sync, repo clone, runner auth verification, and yaver code config. 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.
dev_environment_clone_start accepts 12 parameters: repos, dryRun, target, verify, runnerIds, syncKinds, configKeys, skipConfigs, configureCode, installMissing, sourceDeviceId, targetDeviceId. 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 dev_environment_clone_start: 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.
dev_environment_clone_start 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 dev_environment_clone_start 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 dev_environment_clone_start. 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.
dev_environment_clone_start 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.