wire_detect
List USB-cable-attached iPhones/iPads (xcrun devicectl, falls back to xctrace) plus Android devices (adb devices -l) on the agent's host machine. Skips simulators/emulators and WiFi-paired devices. Returns {devices:[{udid,name,platform,os}], count, hint}. Useful before calling wire_push to know w...
This record as markdown: /tools/io-github-kivanccakmak-yaver/wire-detect.md
What wire_detect does on Yaver
AI agents call wire_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 wire_detect is rated Low
wire_detect purely enumerates connected physical devices via xcrun devicectl and adb without modifying state, executing code, or causing side effects. It is a reconnaissance/discovery tool that gathers information to inform subsequent actions (as noted: 'Useful before calling wire_push'). This fits the Read category: retrieves or queries data with no side effects.
From the tool's definition Tool description states it 'List[s] USB-cable-attached iPhones/iPads... plus Android devices' and 'Returns {devices:[...], count, hint}'. The verb 'list' and return of device metadata with no modification capability indicates a read-only query operation.
Attacks that exploit this kind of access
The rule that runs wire_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 wire_detect, this is the rule to start with:
wire_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 wire_detect call is checked against it from then on.
Questions about wire_detect
List USB-cable-attached iPhones/iPads (xcrun devicectl, falls back to xctrace) plus Android devices (adb devices -l) on the agent's host machine. Skips simulators/emulators and WiFi-paired devices. Returns {devices:[{udid,name,platform,os}], count, hint}. Useful before calling wire_push to know which device IDs you can target. Same data the CLI's yaver wire detect --json returns. 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 wire_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.
wire_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 wire_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 wire_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.
wire_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