Build/verify/upload Yaver platform-specific mobile surfaces. target=tv runs Android TV + tvOS, android-tv verifies leanback metadata and uploads the shared Play AAB, tvos archives/uploads the standalone Apple TV app, and wear-os builds/uploads the Wear OS watch-only AAB to Play internal. Use mobi...
AI agents invoke mobile_platform_deploy 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 |
|---|---|---|---|
target | string | Yes | Executable platform surface target. |
upload | boolean | — | When true, submit store upload after build/verification. Default false for MCP safety. |
dry_run | boolean | — | Return the plan without running the script. |
directory | string | — | Repo root. Empty = current yaver repo. |
timeout_sec | integer | — | Execution timeout. Default 1800 seconds. |
Parameters from the server's own tool schema.
mobile_platform_deploy triggers real processes with real consequences. An agent gone sideways doesn't fire it once — it starts dozens of builds, sends mass notifications, or burns through compute before anyone looks up.
Risk signalsAccepts file system path (directory)
Attacks that exploit this kind of access
Build/verify/upload Yaver platform-specific mobile surfaces. target=tv runs Android TV + tvOS, android-tv verifies leanback metadata and uploads the shared Play AAB, tvos archives/uploads the standalone Apple TV app, and wear-os builds/uploads the Wear OS watch-only AAB to Play internal. Use mobile_platform_matrix first for car/watch readiness. Use dry_run=true to inspect the exact script plan. For build-only verification, pass upload=false. 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_platform_deploy accepts 5 parameters: target, upload, dry_run, directory, timeout_sec. Required: target. 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_platform_deploy: 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_platform_deploy 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_platform_deploy 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_platform_deploy. 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_platform_deploy 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.