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 Magar...
AI agents use remote_dev_prepare 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 |
|---|---|---|---|
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.
An AI agent can call remote_dev_prepare faster than any human can review — one bad instruction and it creates or modifies resources in Yaver by the hundred, each call as confident as the last.
Risk signalsAccepts file system path (dir) · High parameter count (11 properties)
Attacks that exploit this kind of access
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 Write tool in the Yaver MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
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.
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.
remote_dev_prepare 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 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.
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.
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.