adb_push_file · Openclaw Adb MCP: Risk & Policy

WHAT IT DOES

What adb_push_file does on Openclaw Adb

AI agents use adb_push_file to create or update resources in Openclaw Adb — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Openclaw Adb environment.

WHY IT NEEDS A POLICY

Why adb_push_file needs a policy

This tool writes data (files) to an Android device, which is reversible via deletion or overwrite. While it could potentially be abused to install malicious files or overwrite critical system files (which might approach Execute or Destructive territory depending on what gets pushed), the tool itself is fundamentally a Write operation—it creates or modifies files.

From the tool's definition Tool description explicitly states 'Push a file from local machine to the Android device' — this transfers and writes files to a target device. The adb_push_file capability enables file creation/modification on the Android device without deletion.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

adb_push_file Rate-limited

adb_push_file stays usable, but capped — an agent stuck in a loop can't make hundreds of changes 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_push_file": {
      "limits": [
        {
          "counter": "adb_push_file_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

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_push_file

What does the adb_push_file tool do? +

Push a file from local machine to the Android device. It is categorised as a Write tool in the Openclaw Adb MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on adb_push_file? +

Register the Openclaw Adb MCP server in PolicyLayer and add a rule for adb_push_file: 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_push_file? +

adb_push_file is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit adb_push_file? +

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

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

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