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 ...
AI agents use wireless_setup_android 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 |
|---|---|---|---|
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.
An AI agent can call wireless_setup_android 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 freeform code/query input (code)
Attacks that exploit this kind of access
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 Write tool in the Yaver MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
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.
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.
wireless_setup_android 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 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.
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.
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.