This record as markdown: /tools/io-github-kivanccakmak-yaver/adb-screenshot.md
What adb_screenshot does on Yaver
AI agents call adb_screenshot 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 | — |
Parameters from the server's own tool schema.
Why adb_screenshot is rated Low
This tool captures and retrieves visual data from a device without modifying state, executing code, or causing destructive changes. It is purely a read operation that returns image data. Severity is low because screenshots of a local dev device pose minimal security risk in a development context, though they could reveal sensitive UI elements if the device displays credentials or private information.
From the tool's definition Tool name 'adb_screenshot' and description 'Take a screenshot from an Android device' indicate image capture and retrieval only.
Attacks that exploit this kind of access
The rule that runs adb_screenshot 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 adb_screenshot, this is the rule to start with:
adb_screenshot 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 adb_screenshot call is checked against it from then on.
Questions about adb_screenshot
Take a screenshot from an Android device. It is categorised as a Read tool in the Yaver MCP Server, which means it retrieves data without modifying state.
adb_screenshot 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 adb_screenshot: 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.
adb_screenshot 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 adb_screenshot 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 adb_screenshot. 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.
adb_screenshot 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