wireless_connect_android
Reconnect a previously-paired Android phone over WiFi. Use this when wireless_detect shows the phone as visible-unpaired but it was paired in a past session (e.g. after a phone reboot). Empty ip_port = auto-discover via mDNS.
This record as markdown: /tools/io-github-kivanccakmak-yaver/wireless-connect-android.md
What wireless_connect_android does on Yaver
AI agents invoke wireless_connect_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 |
|---|---|---|---|
ip_port | string | — | Connect host:port from the phone's main Wireless debugging screen. Empty = auto-discover via mDNS. |
Parameters from the server's own tool schema.
Why wireless_connect_android is rated High
This tool initiates an active network connection to an Android device, which is an external operation with side effects (establishing a wireless debug/dev session). It is not merely reading data, and it triggers an operation whose effects depend on arguments (ip_port). It falls under Execute as it connects to and interfaces with an external system.
From the tool's definition 'Reconnect a previously-paired Android phone over WiFi' and 'auto-discover via mDNS' — triggers an external network connection operation to a physical device
Attacks that exploit this kind of access
The rule that runs wireless_connect_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_connect_android, this is the rule to start with:
wireless_connect_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.
The button opens the PolicyLayer dashboard: create your workspace, connect Yaver, apply this rule, and every wireless_connect_android call is checked against it from then on.
Questions about wireless_connect_android
Reconnect a previously-paired Android phone over WiFi. Use this when wireless_detect shows the phone as visible-unpaired but it was paired in a past session (e.g. after a phone reboot). Empty ip_port = auto-discover via mDNS. 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.
wireless_connect_android accepts 1 parameter: ip_port. 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_connect_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_connect_android is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the wireless_connect_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_connect_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_connect_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.
More on Yaver, and thousands of servers like it.
Across the catalogue