wireless_connect_android · Yaver MCP: Risk & Policy

WHAT IT DOES

What wireless_connect_android does on Yaver

AI agents use wireless_connect_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.

PARAMETERS

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 IT NEEDS A POLICY

Why wireless_connect_android needs a policy

An AI agent can call wireless_connect_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.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

wireless_connect_android Rate-limited

wireless_connect_android stays usable, but capped — an agent stuck in a loop can't make hundreds of changes 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_connect_android": {
      "limits": [
        {
          "counter": "wireless_connect_android_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Yaver, so you can run agents against it safely.

FAQ

Questions about wireless_connect_android

What does the wireless_connect_android tool do? +

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 Write tool in the Yaver MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

What parameters does wireless_connect_android accept? +

wireless_connect_android accepts 1 parameter: ip_port. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on wireless_connect_android? +

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.

What risk level is wireless_connect_android? +

wireless_connect_android is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit wireless_connect_android? +

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.

How do I block wireless_connect_android completely? +

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.

What MCP server provides wireless_connect_android? +

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.