droid_ui_elements

SERVERYaver SOURCEyaver-cli

Low RISK CLASS

Category Read

Parameters 30 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-ui-elements.md

WHAT IT DOES

What droid_ui_elements does on Yaver

AI agents call droid_ui_elements 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
`limit`	integer	—	Maximum nodes, default 120, max 250
`device`	string	—	adb serial (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.

RISK

Why droid_ui_elements is rated Low

Reads Android UI structure non-destructively; no data modification or execution capability.

From the tool's definition Inspect...hierarchy...Read-only. Password nodes flagged; never persist.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs droid_ui_elements 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_ui_elements, this is the rule to start with:

droid_ui_elements Allowed

droid_ui_elements 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_ui_elements": {}
  }
}

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_ui_elements call is checked against it from then on.

FAQ

Questions about droid_ui_elements

What does the droid_ui_elements tool do? +

Inspect the current Android accessibility hierarchy as structured visible/actionable nodes with labels, resource ids, bounds, and clickable/enabled flags. Read-only. Password nodes are flagged; never persist their values. It is categorised as a Read tool in the Yaver MCP Server, which means it retrieves data without modifying state.

What parameters does droid_ui_elements accept? +

droid_ui_elements accepts 3 parameters: limit, device, device_id. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on droid_ui_elements? +

Register the Yaver MCP server in PolicyLayer and add a rule for droid_ui_elements: 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_ui_elements? +

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

Can I rate-limit droid_ui_elements? +

Yes. Add a rate_limit block to the droid_ui_elements 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_ui_elements completely? +

Set action: deny in the PolicyLayer policy for droid_ui_elements. 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_ui_elements? +

droid_ui_elements 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 678 Yaver tools →

Across the catalogue

The MCP Attack Database →

Guides

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