connect_adb_device · Maa MCP: Risk & Policy

WHAT IT DOES

What connect_adb_device does on MaaMCP

AI agents invoke connect_adb_device to trigger actions in MaaMCP. 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_adb_device needs a policy

Based on the tool name and server context (MaaFramework-based MCP server for Android device automation), this tool likely establishes an ADB (Android Debug Bridge) connection to an Android device, which triggers an external operation. ADB connections enable control over Android devices, making this an Execute-category tool. Severity is high because connecting to a device opens the door for full device control.

From the tool's definition Tool name 'connect_adb_device' on a server providing Android device automation capabilities; description is empty.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

connect_adb_device Rate-limited

connect_adb_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_adb_device": {
      "limits": [
        {
          "counter": "connect_adb_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 MaaMCP, so you can run agents against it safely.

FAQ

Questions about connect_adb_device

What does the connect_adb_device tool do? +

connect_adb_device. It is categorised as a Execute tool in the MaaMCP 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_adb_device? +

Register the Maa MCP server in PolicyLayer and add a rule for connect_adb_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 MaaMCP. Nothing to install.

What risk level is connect_adb_device? +

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

Can I rate-limit connect_adb_device? +

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

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

connect_adb_device is provided by the Maa MCP server (maa-ai/maamcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.