droid_ui_texts
Dump the current Android view hierarchy (uiautomator) and return the on-screen text values — useful for reading login fields / labels / OTP prompts without OCR.
This record as markdown: /tools/io-github-kivanccakmak-yaver/droid-ui-texts.md
What droid_ui_texts does on Yaver
AI agents call droid_ui_texts 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.
Why droid_ui_texts is rated Low
This tool retrieves UI text from the Android device's accessibility tree using uiautomator, a non-invasive inspection API. It has no capability to modify device state, execute commands, or trigger actions — only to query and display visible text.
From the tool's definition Tool description explicitly states it "Dump[s] the current Android view hierarchy" and "return[s] the on-screen text values" — retrieval operations with no modification or side effects.
Attacks that exploit this kind of access
The rule that runs droid_ui_texts 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_texts, this is the rule to start with:
droid_ui_texts 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_ui_texts call is checked against it from then on.
Questions about droid_ui_texts
Dump the current Android view hierarchy (uiautomator) and return the on-screen text values — useful for reading login fields / labels / OTP prompts without OCR. It is categorised as a Read tool in the Yaver MCP Server, which means it retrieves data without modifying state.
droid_ui_texts accepts 1 parameter: device. 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_ui_texts: 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_ui_texts 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_ui_texts 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_ui_texts. 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_ui_texts 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