droid_frame
Capture the current Android screen and return it as a base64 PNG image (via adb exec-out screencap). Use to see what the human/device is looking at.
This record as markdown: /tools/io-github-kivanccakmak-yaver/droid-frame.md
What droid_frame does on Yaver
AI agents call droid_frame 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_frame is rated Low
This tool captures and reads screen content without modifying, executing code, deleting data, or affecting device state. It is a passive observation mechanism analogous to taking a screenshot. While it could reveal sensitive information if the screen displays private data, the tool itself performs only a read operation with no capability to alter device state, execute commands, or cause irreversible changes.
From the tool's definition Tool description states: 'Capture the current Android screen and return it as a base64 PNG image'. The operation is purely observational (screencap), retrieves visual data, and produces no side effects on the device.
Attacks that exploit this kind of access
The rule that runs droid_frame 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_frame, this is the rule to start with:
droid_frame 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_frame call is checked against it from then on.
Questions about droid_frame
Capture the current Android screen and return it as a base64 PNG image (via adb exec-out screencap). Use to see what the human/device is looking at. It is categorised as a Read tool in the Yaver MCP Server, which means it retrieves data without modifying state.
droid_frame 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_frame: 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_frame 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_frame 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_frame. 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_frame 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