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.

SERVERYaver SOURCEyaver-cli

Low RISK CLASS

Category Read

Parameters 10 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/io-github-kivanccakmak-yaver/droid-status.md

WHAT IT DOES

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 (default: first attached device)

Parameters from the server's own tool schema.

RISK

Why droid_status is rated Low

This tool only queries and returns device metadata and current state. It has no side effects, does not execute commands, does not modify data, and does not access financial systems. It is purely informational for monitoring a paired Android device's status during development workflows.

From the tool's definition Tool retrieves device status information: 'Status of the paired Android device... serial, screen width/height, focused activity, and the HTTP frame/input paths'.

Attacks that exploit this kind of access

RECOMMENDED RULE

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 Allowed

droid_status is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "droid_status": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

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.

FAQ

Questions about droid_status

What does the droid_status tool do? +

What parameters does droid_status accept? +

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

How do I enforce a policy on droid_status? +

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.

What risk level is droid_status? +

droid_status is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit droid_status? +

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.

How do I block droid_status completely? +

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.

What MCP server provides droid_status? +

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.

KEEP EXPLORING

More on Yaver, and thousands of servers like it.

This server

All 645 Yaver tools →

Across the catalogue

claude_git_status on Claude Bridge →get_task_status on 0rca Dojo MCP Server → The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →