wireless_detect
List WiFi-paired iPhones/iPads (xcrun devicectl over network) AND Android devices (adb devices), PLUS Android devices that are visible on the local network via mDNS but haven't been adb-paired with this machine yet. Each entry has a status field: 'paired' (ready for wireless_push) or 'visible-unp...
This record as markdown: /tools/io-github-kivanccakmak-yaver/wireless-detect.md
What wireless_detect does on Yaver
AI agents call wireless_detect to retrieve information from Yaver without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why wireless_detect is rated Low
wireless_detect performs device enumeration and status checking only. It retrieves information about paired and visible devices on the local network but does not execute commands on those devices, create/modify configurations, delete anything, or commit financial operations. The mention of 'status field' confirms it is purely informational. This is a typical Read operation: list, query, fetch.
From the tool's definition The tool 'List WiFi-paired iPhones/iPads' and 'list Android devices' — it queries and enumerates connected or discoverable devices without modifying, deleting, or executing operations on them.
Attacks that exploit this kind of access
The rule that runs wireless_detect 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_detect, this is the rule to start with:
wireless_detect is read-only, so it stays allowed. 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_detect call is checked against it from then on.
Questions about wireless_detect
List WiFi-paired iPhones/iPads (xcrun devicectl over network) AND Android devices (adb devices), PLUS Android devices that are visible on the local network via mDNS but haven't been adb-paired with this machine yet. Each entry has a status field: 'paired' (ready for wireless_push) or 'visible-unpaired' (call wireless_setup_android first). Use this BEFORE wireless_push to confirm the target is paired; if you see visible-unpaired entries, prompt the user via yaver_ask_user to tap 'Pair device with pairing code' on the phone, then call wireless_setup_android with the 6-digit code. It is categorised as a Read tool in the Yaver MCP Server, which means it retrieves data without modifying state.
Register the Yaver MCP server in PolicyLayer and add a rule for wireless_detect: 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_detect is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the wireless_detect 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_detect. 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_detect 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.
This server
Across the catalogue