wireless_setup_android

SERVERYaver SOURCEyaver-cli

High RISK CLASS

Category Execute

Parameters 21 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-setup-android.md

WHAT IT DOES

What wireless_setup_android does on Yaver

AI agents invoke wireless_setup_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 on the phone's 'Pair device with pairing code' screen.
`poll_seconds`	integer	—	How long to wait for the pairing service to appear in mDNS. Default 120, max 300.

Parameters from the server's own tool schema.

RISK

Why wireless_setup_android is rated High

The tool executes external shell commands (adb pair, adb connect) and performs mDNS polling to establish a wireless debugging bridge to an Android device. This constitutes execution of system-level operations with significant blast radius — a misused or spoofed pairing code could connect an agent to an unintended device or expose the device to ADB-level control.

From the tool's definition runs `adb pair`, then auto-resolves the matching connect endpoint and runs `adb connect`

Risk signalsAccepts freeform code/query input (code)

Attacks that exploit this kind of access

RECOMMENDED RULE

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

wireless_setup_android Rate-limited

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

FAQ

Questions about wireless_setup_android

What does the wireless_setup_android tool do? +

First-time Android wireless pairing for AI agents. Prerequisite: the user has tapped 'Pair device with pairing code' on the phone (Settings → Developer options → Wireless debugging) and read off the 6-digit code. This tool polls mDNS for the pairing service, runs adb pair, then auto-resolves the matching connect endpoint and runs adb connect. Returns the post-setup device list so you can verify pairing in one round trip. Use yaver_ask_user to collect the code BEFORE calling this — never make up a code. 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_setup_android accept? +

wireless_setup_android accepts 2 parameters: code, poll_seconds. Required: code. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on wireless_setup_android? +

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

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

Can I rate-limit wireless_setup_android? +

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

Set action: deny in the PolicyLayer policy for wireless_setup_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_setup_android? +

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