dev_environment_clone_start

Start cloning a coding-focused Yaver dev environment. Reuses toolchain sync, repo clone, runner auth verification, and yaver code config.

SERVERYaver SOURCEyaver-cli

High RISK CLASS

Category Execute

Parameters 120 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/dev-environment-clone-start.md

WHAT IT DOES

What dev_environment_clone_start does on Yaver

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.

RISK

Why dev_environment_clone_start is rated High

This tool executes a multi-step development environment setup process (toolchain sync, repo cloning, auth verification, configuration). While not destructive per se, it runs external operations with side effects that could include installing code, modifying local state, and provisioning cloud/remote resources.

From the tool's definition Tool description states it 'Start[s] cloning a coding-focused Yaver dev environment' involving 'repo clone, runner auth verification, and yaver code config' — these are operations that trigger external processes (cloning repositories, verifying…

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

RECOMMENDED RULE

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

dev_environment_clone_start Rate-limited

dev_environment_clone_start 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": {
    "dev_environment_clone_start": {
      "limits": [
        {
          "counter": "dev_environment_clone_start_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 dev_environment_clone_start call is checked against it from then on.

FAQ

Questions about dev_environment_clone_start

What does the dev_environment_clone_start tool do? +

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.

What parameters does dev_environment_clone_start accept? +

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.

How do I enforce a policy on dev_environment_clone_start? +

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.

What risk level is dev_environment_clone_start? +

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

Can I rate-limit dev_environment_clone_start? +

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.

How do I block dev_environment_clone_start completely? +

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.

What MCP server provides dev_environment_clone_start? +

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.

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

start_devtools_monitoring on Percepta MCP Server →team_manager_start_room on Team Manager MCP →start_etw_trace on Procmon → All high-risk MCP tools → The MCP Attack Database →

Guides

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