mobile_deploy_to_phone
One-shot "put my app on my phone": take the React Native / Expo app in this directory and get it running inside the Yaver app on the paired phone — no TestFlight, no Xcode, no native install. Chains the whole Hermes flow in order: checks the project (mobile_project_status), installs dependencies ...
This record as markdown: /tools/io-github-kivanccakmak-yaver/mobile-deploy-to-phone.md
What mobile_deploy_to_phone does on Yaver
AI agents invoke mobile_deploy_to_phone 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 |
|---|---|---|---|
mode | string | — | Reload mode passed to the final step: "dev" (Metro fast-refresh, default) or "bundle". |
platform | string | — | Target platform for the Hermes bundle: "ios" (default) or "android". |
device_id | string | — | Optional owned Yaver device id/name/alias to build on. Empty = this machine (the common case: agent, project, and daemon all local). |
directory | string | — | Project directory (default: agent work dir). Should be a React Native / Expo app or a monorepo containing one (apps/mobile, mobile/, …). |
framework | string | — | Optional framework override (expo or react-native); auto-detected when omitted. |
plan_only | boolean | — | When true, run only the fast checks (status/prepare/doctor) and return the ordered remaining steps instead of running the slow build + reload. Use when your too |
Parameters from the server's own tool schema.
Why mobile_deploy_to_phone is rated High
This tool executes a multi-stage deployment pipeline including dependency installation, compilation, and deployment to a physical device. While primarily intended for legitimate development use, misuse could compile and deploy malicious code to a paired mobile device. The blast radius depends on app contents and phone permissions.
From the tool's definition Tool 'mobile_deploy_to_phone' performs code compilation and deployment via 'Chains the whole Hermes flow': checks project, installs dependencies, diagnoses blockers, compiles Hermes bundle, and reloads onto the phone.
Risk signalsAccepts file system path (directory)
Attacks that exploit this kind of access
The rule that runs mobile_deploy_to_phone 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 mobile_deploy_to_phone, this is the rule to start with:
mobile_deploy_to_phone 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.
The button opens the PolicyLayer dashboard: create your workspace, connect Yaver, apply this rule, and every mobile_deploy_to_phone call is checked against it from then on.
Questions about mobile_deploy_to_phone
One-shot "put my app on my phone": take the React Native / Expo app in this directory and get it running inside the Yaver app on the paired phone — no TestFlight, no Xcode, no native install. Chains the whole Hermes flow in order: checks the project (mobile_project_status), installs dependencies if missing (mobile_project_prepare), diagnoses blockers and native-module compatibility (mobile_hermes_doctor), compiles the Hermes bundle (mobile_project_build), and reloads it onto the phone (mobile_hermes_reload). Stops at the first blocker and returns a single next_action sentence plus a per-step trace. This is the verb to call when a human says "deploy/preview my app on my phone" — prefer it over calling the five mobile_* tools by hand. The phone must have the Yaver app open and signed in with the same account. Returns { ok, done, steps[], blockers?, next_actions?, next_action }. 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.
mobile_deploy_to_phone accepts 6 parameters: mode, platform, device_id, directory, framework, plan_only. 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 mobile_deploy_to_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.
mobile_deploy_to_phone 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 mobile_deploy_to_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 mobile_deploy_to_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.
mobile_deploy_to_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.
More on Yaver, and thousands of servers like it.
Across the catalogue