Low Risk

adb_devices

List all connected Android devices with model, Android version, and screen size.

How to control adb_devices ↓

What adb_devices does on Claude Pascal MCP Server

AI agents call adb_devices to retrieve information from Claude Pascal MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Low Risk

Why adb_devices needs a policy

This tool performs a read-only operation that queries and returns metadata about connected devices. There are no side effects, no code execution, no data modification, and no destructive actions. The blast radius of misuse is minimal — an attacker gains only informational inventory of connected devices, which is low-risk compared to other tools on this server (adb_install, adb_push, adb_launch_app, etc.).

From the tool's definition Tool description states it 'List all connected Android devices with model, Android version, and screen size' — a query operation that retrieves device information without modifying or executing anything.

Documented attack patterns abuse exactly the kind of access adb_devices gives an agent:

How to control adb_devices

PolicyLayer is an MCP gateway — it sits between your AI agents and Claude Pascal MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for adb_devices:

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "adb_devices": {}
  }
}

adb_devices is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.

  1. Create a free account and register Claude Pascal MCP Server — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
CAP THIS TOOL →

Free to start. No card required.

Related tools and policies

Go deeper

Questions about adb_devices

What does the adb_devices tool do? +

List all connected Android devices with model, Android version, and screen size. It is categorised as a Read tool in the Claude Pascal MCP Server MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on adb_devices? +

Register the Claude Pascal MCP Server 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 Claude Pascal MCP Server. 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 Claude Pascal MCP Server MCP server (tina4stack/claude-pascal-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Claude Pascal MCP Server tool call.

Start from Claude Pascal MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

Free to start. No card required.

53 Claude Pascal MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.

// GET IN TOUCH

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

Message sent.

We'll get back to you soon.