reload_adb_server · MCP Emulator Controller MCP

WHAT IT DOES

What reload_adb_server does on MCP Emulator Controller

AI agents invoke reload_adb_server to trigger actions in MCP Emulator Controller. 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 reload_adb_server needs a policy

Reloading/restarting ADB server is an Execute action: it runs an external operation (kill/restart) with effects that depend on arguments and current state. It's not Read (no data retrieval), not Write (doesn't create/modify persistent data reversibly), not Destructive (doesn't irreversibly delete data), and not Financial.

From the tool's definition Tool performs 'kill and restart' of ADB server—a system-level operation that interrupts running processes and restarts a critical service. This is an external operation whose effects depend on system state.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

reload_adb_server Rate-limited

reload_adb_server 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": {
    "reload_adb_server": {
      "limits": [
        {
          "counter": "reload_adb_server_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 MCP Emulator Controller, so you can run agents against it safely.

FAQ

Questions about reload_adb_server

What does the reload_adb_server tool do? +

Reload ADB server (kill and restart). It is categorised as a Execute tool in the MCP Emulator Controller MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on reload_adb_server? +

Register the MCP Emulator Controller MCP server in PolicyLayer and add a rule for reload_adb_server: 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 MCP Emulator Controller. Nothing to install.

What risk level is reload_adb_server? +

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

Can I rate-limit reload_adb_server? +

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

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

reload_adb_server is provided by the MCP Emulator Controller MCP server (teemo4621/mcp-emulator-controller). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.