wireless_pair_android

SERVERYaver SOURCEyaver-cli

High RISK CLASS

Category Execute

Parameters 32 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-pair-android.md

WHAT IT DOES

What wireless_pair_android does on Yaver

AI agents invoke wireless_pair_android 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
`code`	string	Yes	The 6-digit pairing code shown next to the pair host:port on the phone.
`ip_port`	string	Yes	The PAIR host:port from the phone's 'Pair device with pairing code' screen — NOT the connect port from the main Wireless debugging screen.
`auto_connect`	boolean	—	After pairing, auto-resolve the connect endpoint via mDNS and run adb connect. Default true.

Parameters from the server's own tool schema.

RISK

Why wireless_pair_android is rated High

The tool executes an adb pairing and connection command against an Android device. This triggers an external operation (adb connect) whose effects depend on the supplied host:port arguments. It is not merely reading data, and while it modifies device connectivity state, the primary action is executing an external system command (adb).

From the tool's definition 'runs adb connect immediately' and 'auto_connect=true (default), this tool also resolves the matching connect entry and runs adb connect immediately'

Risk signalsAccepts freeform code/query input (code)

Attacks that exploit this kind of access

RECOMMENDED RULE

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

wireless_pair_android Rate-limited

wireless_pair_android 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_pair_android": {
      "limits": [
        {
          "counter": "wireless_pair_android_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_pair_android call is checked against it from then on.

FAQ

Questions about wireless_pair_android

What does the wireless_pair_android tool do? +

Manual one-shot Android wireless pair when you already know the pair host:port (e.g. user typed it from the phone screen). Prefer wireless_setup_android when you don't have the host:port yet — it auto-discovers via mDNS. The pair port is DIFFERENT from the connect port shown on the main Wireless debugging screen. With auto_connect=true (default), this tool also resolves the matching connect entry and runs adb connect immediately, returning a single ready-to-use paired device. 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_pair_android accept? +

wireless_pair_android accepts 3 parameters: code, ip_port, auto_connect. Required: code, ip_port. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on wireless_pair_android? +

Register the Yaver MCP server in PolicyLayer and add a rule for wireless_pair_android: 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_pair_android? +

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

Can I rate-limit wireless_pair_android? +

Yes. Add a rate_limit block to the wireless_pair_android 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_pair_android completely? +

Set action: deny in the PolicyLayer policy for wireless_pair_android. 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_pair_android? +

wireless_pair_android 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 →