connect_to_device · Android Forensics ADB MCP Server MCP

WHAT IT DOES

What connect_to_device does on Android Forensics ADB MCP Server

AI agents invoke connect_to_device to trigger actions in Android Forensics ADB MCP Server. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.

WHY IT NEEDS A POLICY

Why connect_to_device needs a policy

Establishing a device connection triggers an external operation (ADB connection to a physical/remote Android device). It has no read/write/destructive effect on its own, but it enables all subsequent forensic operations and represents an active external interaction rather than a passive query.

From the tool's definition Connect to a specific Android device or the first available device

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

connect_to_device Rate-limited

connect_to_device stays usable, but rate-capped — a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "connect_to_device": {
      "limits": [
        {
          "counter": "connect_to_device_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Android Forensics ADB MCP Server, so you can run agents against it safely.

FAQ

Questions about connect_to_device

What does the connect_to_device tool do? +

Connect to a specific Android device or the first available device. It is categorised as a Execute tool in the Android Forensics ADB MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on connect_to_device? +

Register the Android Forensics ADB MCP Server MCP server in PolicyLayer and add a rule for connect_to_device: 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 Android Forensics ADB MCP Server. Nothing to install.

What risk level is connect_to_device? +

connect_to_device is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit connect_to_device? +

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

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

connect_to_device is provided by the Android Forensics ADB MCP Server MCP server (0x-professor/droidforensics-suite). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

// THE FULL RECORD

connect_to_device is one line of Android Forensics ADB MCP Server's registry record.

The record carries the whole server: verified identity, auth posture, risk grade, every tool classified, recommended policy — re-checked continuously.

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