adb_screencap_annotated
Take a screenshot with UI element bounding boxes and numbered labels composited directly onto the image. Returns the annotated PNG path plus a text legend mapping each element number to its identity. Ideal for LLM workflows that need to reference specific UI elements by number rather than by coor...
This record as markdown: /tools/io-github-fullread-deepadb/adb-screencap-annotated.md
What adb_screencap_annotated does on Deepadb
AI agents call adb_screencap_annotated to retrieve information from Deepadb without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why adb_screencap_annotated is rated Low
This tool captures and retrieves visual data from the device display. While it executes the screencap operation on the device, the operation itself has no side effects on device state, data, or system behavior. It is informational/observational only, similar to a camera snapshot. No data is modified, deleted, or executed based on user input.
From the tool's definition Tool takes a screenshot with annotations and returns PNG path plus text legend mapping elements to identities. No modification, deletion, or execution of device operations—purely retrieves visual state of the UI.
Attacks that exploit this kind of access
The rule that runs adb_screencap_annotated safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Deepadb, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For adb_screencap_annotated, this is the rule to start with:
adb_screencap_annotated 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 Deepadb, apply this rule, and every adb_screencap_annotated call is checked against it from then on.
Questions about adb_screencap_annotated
Take a screenshot with UI element bounding boxes and numbered labels composited directly onto the image. Returns the annotated PNG path plus a text legend mapping each element number to its identity. Ideal for LLM workflows that need to reference specific UI elements by number rather than by coordinates. It is categorised as a Read tool in the Deepadb MCP Server, which means it retrieves data without modifying state.
Register the Deepadb MCP server in PolicyLayer and add a rule for adb_screencap_annotated: 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 Deepadb. Nothing to install.
adb_screencap_annotated 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_screencap_annotated 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_screencap_annotated. 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_screencap_annotated is provided by the Deepadb MCP server (deepadb). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Deepadb, and thousands of servers like it.
This server
Across the catalogue