adb_test_session_start
Start a structured test session. Creates a named directory for organizing numbered screenshots and logcat captures.
This record as markdown: /tools/io-github-fullread-deepadb/adb-test-session-start.md
What adb_test_session_start does on Deepadb
AI agents use adb_test_session_start to create or update resources in Deepadb, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Deepadb environment.
Why adb_test_session_start is rated Medium
This tool creates a new directory structure on the device/host filesystem to organize test artifacts. It is a Write operation (creating a directory and session metadata) with low severity since it only initializes a test session folder and does not modify existing data, execute arbitrary code, or have destructive effects.
From the tool's definition Creates a named directory for organizing numbered screenshots and logcat captures
Attacks that exploit this kind of access
The rule that runs adb_test_session_start 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_session_start, this is the rule to start with:
adb_test_session_start stays usable, but capped: an agent stuck in a loop can't make hundreds of changes a minute. 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_session_start call is checked against it from then on.
Questions about adb_test_session_start
Start a structured test session. Creates a named directory for organizing numbered screenshots and logcat captures. It is categorised as a Write tool in the Deepadb MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Deepadb MCP server in PolicyLayer and add a rule for adb_test_session_start: 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_session_start is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the adb_test_session_start 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_session_start. 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_session_start 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