This record as markdown: /tools/io-github-kivanccakmak-yaver/adb-devices.md
What adb_devices does on Yaver
AI agents call adb_devices to retrieve information from Yaver 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 is a read-only tool that enumerates connected devices. It has no side effects, does not execute code, and does not modify any state. The blast radius of misuse is minimal—an attacker gains only visibility into what devices are available, not control over them.
From the tool's definition Tool name 'adb_devices' and description 'List connected Android devices/emulators' indicate a query operation that retrieves device information without modifying or executing anything.
Attacks that exploit this kind of access
The rule that runs adb_devices safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Yaver, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For adb_devices, this is the rule to start with:
adb_devices 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 Yaver, apply this rule, and every adb_devices call is checked against it from then on.
Questions about adb_devices
List connected Android devices/emulators. It is categorised as a Read tool in the Yaver MCP Server, which means it retrieves data without modifying state.
Register the Yaver 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 Yaver. Nothing to install.
adb_devices 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_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.
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.
adb_devices is provided by the Yaver MCP server (yaver-cli). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Yaver, and thousands of servers like it.
This server
Across the catalogue