adb_device_state

SERVERDeepadb SOURCEdeepadb

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/io-github-fullread-deepadb/adb-device-state.md

WHAT IT DOES

What adb_device_state does on Deepadb

AI agents call adb_device_state 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.

RISK

Why adb_device_state is rated Low

The tool queries device status information with no side effects. It is explicitly designed to gather diagnostic data about the device's current state, which is a read-only operation. While running on ADB gives it access to device internals, it cannot modify data, execute commands, delete resources, or trigger financial transactions.

From the tool's definition Tool performs 'Get a combined device state snapshot' and describes it as a 'pre-check' and 'quick device health summary', indicating it retrieves information only (battery level, network connectivity, screen state, foreground activity, orientation) without…

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs adb_device_state 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_device_state, this is the rule to start with:

adb_device_state Allowed

adb_device_state is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "adb_device_state": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Deepadb, apply this rule, and every adb_device_state call is checked against it from then on.

FAQ

Questions about adb_device_state

What does the adb_device_state tool do? +

Get a combined device state snapshot in one call: battery level/status, network connectivity, screen on/off, foreground activity, and orientation. Useful as a pre-check before UI automation or as a quick device health summary. It is categorised as a Read tool in the Deepadb MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on adb_device_state? +

Register the Deepadb MCP server in PolicyLayer and add a rule for adb_device_state: 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.

What risk level is adb_device_state? +

adb_device_state is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit adb_device_state? +

Yes. Add a rate_limit block to the adb_device_state 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.

How do I block adb_device_state completely? +

Set action: deny in the PolicyLayer policy for adb_device_state. 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.

What MCP server provides adb_device_state? +

adb_device_state 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.

KEEP EXPLORING

More on Deepadb, and thousands of servers like it.

This server

All 205 Deepadb tools →

Across the catalogue

The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →