wireless_push

SERVERYaver SOURCEyaver-cli

High RISK CLASS

Category Execute

Parameters 60 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/io-github-kivanccakmak-yaver/wireless-push.md

WHAT IT DOES

What wireless_push does on Yaver

AI agents invoke wireless_push 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
`path`	string	—	Project path. Empty = the AI session's working directory (the dir Claude Code / Codex / opencode was started in) — typically what you want when iterating inside
`config`	string	—	Build configuration. Default Release.
`device`	string	—	Specific device UDID (iOS) or wireless serial like '192.168.1.42:5555' (Android). Empty = first paired wireless device for the platform. Run wireless_detect fir
`platform`	string	—	Force a platform when the project supports both. Empty = auto-pick.
`no_launch`	boolean	—	Install but don't launch. Default false.
`timeout_sec`	integer	—	Hard timeout in seconds. Default 1800 (30 min).

Parameters from the server's own tool schema.

RISK

Why wireless_push is rated High

This tool compiles native binaries using xcodebuild/gradle and installs them on a physical device over WiFi. It triggers a full build pipeline and deploys to hardware, which constitutes executing an external operation with significant side effects. Misuse could result in deploying malicious or broken binaries to real devices, making severity high.

From the tool's definition Build a self-contained native binary (xcodebuild Release / gradle installRelease) and install it on a WIFI-paired phone via the agent's host machine. Same long-running build pipeline as wire_push, but routes through the wireless device picker.

Risk signalsAccepts file system path (path)

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs wireless_push 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 wireless_push, this is the rule to start with:

wireless_push Rate-limited

wireless_push 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.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "wireless_push": {
      "limits": [
        {
          "counter": "wireless_push_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Yaver, apply this rule, and every wireless_push call is checked against it from then on.

FAQ

Questions about wireless_push

What does the wireless_push tool do? +

Build a self-contained native binary (xcodebuild Release / gradle installRelease) and install it on a WIFI-paired phone via the agent's host machine. Same long-running build pipeline as wire_push, but routes through the wireless device picker. If no paired wireless device is found, the error includes a count of visible-unpaired devices so you can chain wireless_setup_android. Returns {ok, exit_code, device, platform, transport, stack, log_path, log_tail, elapsed_sec}. 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.

What parameters does wireless_push accept? +

wireless_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.

How do I enforce a policy on wireless_push? +

Register the Yaver MCP server in PolicyLayer and add a rule for wireless_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.

What risk level is wireless_push? +

wireless_push is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit wireless_push? +

Yes. Add a rate_limit block to the wireless_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.

How do I block wireless_push completely? +

Set action: deny in the PolicyLayer policy for wireless_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.

What MCP server provides wireless_push? +

wireless_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.

KEEP EXPLORING

More on Yaver, and thousands of servers like it.

This server

All 645 Yaver tools → High-risk tools on this server →

Across the catalogue

All high-risk MCP tools → The MCP Attack Database →

Guides

Govern code and CI agents →Agent sandbox →Least privilege for MCP →