adb_command · Yaver MCP: Risk & Policy

WHAT IT DOES

What adb_command does on Yaver

AI agents invoke adb_command to trigger actions in Yaver. 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.

PARAMETERS

Parameter	Type	Required	Description
`device`	string	—	Device serial (optional)
`command`	string	Yes	Shell command

Parameters from the server's own tool schema.

WHY IT NEEDS A POLICY

Why adb_command needs a policy

adb_command triggers real processes with real consequences. An agent gone sideways doesn't fire it once — it starts dozens of builds, sends mass notifications, or burns through compute before anyone looks up.

Risk signalsAccepts freeform code/query input (command)

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

adb_command Rate-limited

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

FAQ

Questions about adb_command

What does the adb_command tool do? +

Run a command on an Android device via ADB. It is categorised as a Execute tool in the Yaver MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

What parameters does adb_command accept? +

adb_command accepts 2 parameters: device, command. Required: command. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on adb_command? +

Register the Yaver MCP server in PolicyLayer and add a rule for adb_command: 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.

What risk level is adb_command? +

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

Can I rate-limit adb_command? +

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

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

adb_command 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.