adb_devices

List all connected Android devices with their state, model, and product info

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-devices.md

What adb_devices does on Deepadb

AI agents call adb_devices 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_devices is rated Low

This tool performs a purely informational read operation—it queries and returns device state and metadata (model, product info) without creating, modifying, executing, deleting, or committing financial operations. The blast radius is minimal; misuse would at worst expose what devices are connected, but cannot alter device state or execute commands. This is a standard ADB introspection command.

From the tool's definition Tool name 'adb_devices' and description 'List all connected Android devices with their state, model, and product info' indicate a query/enumeration operation that retrieves device metadata without modification or execution.

Questions about adb_devices

What does the adb_devices tool do? +

List all connected Android devices with their state, model, and product info. 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_devices? +

Register the Deepadb MCP server in PolicyLayer and add a rule for adb_devices: 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_devices? +

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

Can I rate-limit adb_devices? +

Yes. Add a rate_limit block to the adb_devices 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_devices completely? +

Set action: deny in the PolicyLayer policy for adb_devices. 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_devices? +

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

Across the catalogue

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of Deepadb's. Pull the full record:

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.