Build a self-contained native binary (xcodebuild Release / gradle installRelease) and install it on a USB-attached phone via the agent's host machine. No Metro / dev server is involved — JS is bundled into the .app/.apk at build time. Auto-detects the framework (Expo, React Native, Flutter, nativ...
AI agents use wire_push 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 |
|---|---|---|---|
path | string | — | Project path. Empty = the AI session's working directory (the dir Claude Code / Codex / opencode was started in) — typically what you want. Walks one level into |
config | string | — | Build configuration. Default Release (self-contained binary, no Metro). Pass Debug only when iterating with a running Metro dev server. |
device | string | — | Specific device UDID (iOS) or serial (Android). Empty = first attached. Run wire_detect first to see your options. |
platform | string | — | Force a platform when the project supports both. Empty = auto-pick (native projects pick by stack; cross-platform projects pick ios on macOS, android elsewhere) |
no_launch | boolean | — | Install the app but don't launch it after. Default false. |
timeout_sec | integer | — | Hard timeout in seconds. Default 1800 (30 min). Cold-cache xcodebuild + pod install + hermesc compile easily hits 20+ min on first run. |
Parameters from the server's own tool schema.
An AI agent can call wire_push 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 (path)
Attacks that exploit this kind of access
Build a self-contained native binary (xcodebuild Release / gradle installRelease) and install it on a USB-attached phone via the agent's host machine. No Metro / dev server is involved — JS is bundled into the .app/.apk at build time. Auto-detects the framework (Expo, React Native, Flutter, native iOS, native Android) and walks into common subdirs (mobile/, app/, apps/*, packages/*) when the path itself isn't a mobile project. Long-running (5-30 min); captures stdout/stderr to ~/.yaver/logs/wire-push-*.log and returns the path + last 30 lines so you can grep for errors. Returns {ok, exit_code, device, platform, stack, log_path, log_tail, elapsed_sec}. 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.
wire_push accepts 6 parameters: path, config, device, platform, no_launch, timeout_sec. 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 wire_push: 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.
wire_push 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 wire_push 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 wire_push. 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.
wire_push 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.