Take a screenshot of the device screen and return as base64 PNG
AI agents call adb_screenshot to retrieve information from Openclaw Adb without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves visual state information from a device without modifying, deleting, or executing operations on the device itself. It is purely observational and analogous to querying or fetching data. While screenshots could theoretically reveal sensitive information displayed on screen, the tool itself performs no destructive, executable, or state-changing actions.
From the tool's definition Tool name 'adb_screenshot' and description 'Take a screenshot of the device screen and return as base64 PNG' indicates data retrieval with no modification or side effects.
Attacks that exploit this kind of access
Take a screenshot of the device screen and return as base64 PNG. It is categorised as a Read tool in the Openclaw Adb MCP Server, which means it retrieves data without modifying state.
Register the Openclaw Adb 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 Openclaw Adb. 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 Openclaw Adb MCP server (wilsonbeam/openclaw-adb-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →