adb_test_step
Capture a numbered test step: takes a screenshot and captures logcat since the last step. Saves both to the session directory.
This record as markdown: /tools/io-github-fullread-deepadb/adb-test-step.md
What adb_test_step does on Deepadb
AI agents call adb_test_step 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_test_step is rated Low
adb_test_step retrieves information (screenshot and logcat output) and stores it locally for testing/debugging purposes. It has no side effects on the device or data—it does not execute commands, modify settings, delete files, or trigger external operations. The action is purely observational and diagnostic, making it a Read category tool with low severity.
From the tool's definition Tool description states it 'takes a screenshot and captures logcat since the last step. Saves both to the session directory.' These are read-only operations that retrieve diagnostic data without modifying device state.
Attacks that exploit this kind of access
The rule that runs adb_test_step 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_test_step, this is the rule to start with:
adb_test_step 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_test_step call is checked against it from then on.
Questions about adb_test_step
Capture a numbered test step: takes a screenshot and captures logcat since the last step. Saves both to the session directory. 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_test_step: 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_test_step 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_test_step 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_test_step. 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_test_step 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