droid_status
Status of the paired Android device for human-in-the-loop control: serial, screen width/height, focused activity, and the HTTP frame/input paths a remote UI uses. Returns {device:null} when no device is attached. Poll the focus/UI to detect when a human has finished logging in.
This record as markdown: /tools/io-github-kivanccakmak-yaver/droid-status.md
What droid_status does on Yaver
AI agents call droid_status 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.
| Parameter | Type | Required | Description |
|---|---|---|---|
device | string | — | adb serial on that machine (default: first attached device) |
device_id | string | — | Owned Yaver machine hosting the Android target (default: this machine) |
Parameters from the server's own tool schema.
Why droid_status is rated Low
Retrieves device status and UI state without modifying or executing operations.
From the tool's definition Status of paired Android device: serial, screen dimensions, focused activity, HTTP paths.
Attacks that exploit this kind of access
The rule that runs droid_status 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 droid_status, this is the rule to start with:
droid_status 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 droid_status call is checked against it from then on.
Questions about droid_status
Status of the paired Android device for human-in-the-loop control: serial, screen width/height, focused activity, and the HTTP frame/input paths a remote UI uses. Returns {device:null} when no device is attached. Poll the focus/UI to detect when a human has finished logging in. It is categorised as a Read tool in the Yaver MCP Server, which means it retrieves data without modifying state.
droid_status accepts 2 parameters: device, device_id. 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 droid_status: 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.
droid_status 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 droid_status 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 droid_status. 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.
droid_status 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