Personal Agent Gateway: MIRROR the apps from the user's phone onto a clone node (redroid or a second-hand phone) in one step. Derives the clone's desired app-set from the phone's reported inventory (system apps are never mirrored), writes it, and — with sync:true — installs them all Play-sourced....
AI agents use gateway_clone_from_phone 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 |
|---|---|---|---|
mode | string | — | Install path when sync=true: 'play_ui' (default) or 'device_owner' |
sync | boolean | — | Install now (true) or just write the desired set (false, default) |
clone | string | Yes | Target clone node id (redroid/phone adb serial) |
phone | string | Yes | Source phone device id (must have reported an inventory) |
connector_only | boolean | — | Mirror only apps that back a gateway connector (default false = mirror every non-system app) |
Parameters from the server's own tool schema.
An AI agent can call gateway_clone_from_phone 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.
Attacks that exploit this kind of access
Personal Agent Gateway: MIRROR the apps from the user's phone onto a clone node (redroid or a second-hand phone) in one step. Derives the clone's desired app-set from the phone's reported inventory (system apps are never mirrored), writes it, and — with sync:true — installs them all Play-sourced. install ≠ logged in (authorize each app via the gateway login broker afterwards). 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.
gateway_clone_from_phone accepts 5 parameters: mode, sync, clone, phone, connector_only. Required: clone, phone. 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 gateway_clone_from_phone: 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.
gateway_clone_from_phone 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 gateway_clone_from_phone 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 gateway_clone_from_phone. 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.
gateway_clone_from_phone 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.