adb_push · LocalAnt MCP: Risk & Policy

WHAT IT DOES

What adb_push does on LocalAnt

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

WHY IT NEEDS A POLICY

Why adb_push needs a policy

adb_push transfers files from the host to an Android device, which modifies device state. While the description restricts to 'allowed directories', the tool can write arbitrary file content to a device, potentially enabling malware installation, configuration tampering, or data injection attacks. This is reversible (files can be deleted), so it's Write rather than Destructive.

From the tool's definition Tool name 'adb_push' and description 'Push a local file (inside an allowed directory) to the device' indicates file transfer to Android device. The risk level annotation 'Risk 3' suggests elevated concern.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

adb_push Rate-limited

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

FAQ

Questions about adb_push

What does the adb_push tool do? +

Push a local file (inside an allowed directory) to the device. Risk 3. It is categorised as a Write tool in the LocalAnt 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? +

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

What risk level is adb_push? +

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

Can I rate-limit adb_push? +

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

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

adb_push is provided by the LocalAnt MCP server (yuga-hashimoto/localant). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.