adb_install_app · Openclaw Adb MCP: Risk & Policy

WHAT IT DOES

What adb_install_app does on Openclaw Adb

AI agents invoke adb_install_app to trigger actions in Openclaw Adb. 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 adb_install_app needs a policy

Installing an APK executes an external operation that deploys application code onto a device. This can introduce malicious software, bypass security controls, or establish persistence. It is not merely writing data — it triggers the Android package installer and grants the app permissions/capabilities on the device. The blast radius is high since a misused install could deploy malware or spyware.

From the tool's definition Install an APK file on the device

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

adb_install_app Rate-limited

adb_install_app 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_install_app": {
      "limits": [
        {
          "counter": "adb_install_app_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 Openclaw Adb, so you can run agents against it safely.

FAQ

Questions about adb_install_app

What does the adb_install_app tool do? +

Install an APK file on the device. It is categorised as a Execute tool in the Openclaw Adb MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on adb_install_app? +

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

What risk level is adb_install_app? +

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

Can I rate-limit adb_install_app? +

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

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

adb_install_app is provided by the Openclaw Adb MCP server (wilsonbeam/openclaw-adb-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.