remote_dev_prepare

SERVERYaver SOURCEyaver-cli

High RISK CLASS

Category Execute

Parameters 110 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/remote-dev-prepare.md

WHAT IT DOES

What remote_dev_prepare does on Yaver

AI agents invoke remote_dev_prepare 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
`dir`	string	—	Target directory on the remote machine. Defaults to the target agent's repo clone policy.
`branch`	string	—	Branch to clone/checkout. Defaults to current branch when inferable.
`dryRun`	boolean	—	Plan and return actions without applying changes.
`verify`	boolean	—	Verify target capabilities/runners after setup. Default true.
`repoUrl`	string	—	Git repo URL. Defaults to the current MCP cwd's origin when inferable.
`configureCode`	boolean	—	Set cloned repo as target's yaver-code workdir. Default true.
`prepareMobile`	boolean	—	Run mobile_project_prepare on the target after clone. Default false.
`installMissing`	boolean	—	Install missing common toolchain pieces on target before clone. Default false for lightweight setup.
`targetDeviceId`	string	—	Target owned Yaver device id/name/alias. Defaults to primary when omitted.
`mobileDirectory`	string	—	Directory for mobile_project_prepare. Defaults to the cloned repo path.
`includeGitCredentials`	boolean	—	P2P-transfer local git clone credentials to target. Default false; public repos do not need it.

Parameters from the server's own tool schema.

RISK

Why remote_dev_prepare is rated High

This tool performs multiple active operations on a remote/self-hosted device: cloning or updating a repository, configuring a working directory, and installing dependencies. These are external operations triggered on a remote machine, fitting the Execute category.

From the tool's definition clone or update a repo on an owned Yaver device, set that repo as the target's yaver-code workdir, optionally install mobile dependencies

Risk signalsAccepts file system path (dir) · High parameter count (11 properties)

Attacks that exploit this kind of access

RECOMMENDED RULE

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

remote_dev_prepare Rate-limited

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

FAQ

Questions about remote_dev_prepare

What does the remote_dev_prepare tool do? +

One-shot remote/self-hosted dev setup: clone or update a repo on an owned Yaver device, set that repo as the target's yaver-code workdir, optionally install mobile dependencies, and return next MCP actions for browser/mobile testing. This is the preferred flow when a user says to develop on Magara or another self-hosted machine instead of the local computer. 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 remote_dev_prepare accept? +

remote_dev_prepare accepts 11 parameters: dir, branch, dryRun, verify, repoUrl, configureCode, prepareMobile, installMissing, targetDeviceId, mobileDirectory, includeGitCredentials. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on remote_dev_prepare? +

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

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

Can I rate-limit remote_dev_prepare? +

Yes. Add a rate_limit block to the remote_dev_prepare 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 remote_dev_prepare completely? +

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

remote_dev_prepare 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 →