adb_file_push

Push a local file to an Android device using normal ADB permissions.

SERVERJshookmcp SOURCE@jshookmcp/jshook

Medium RISK CLASS

Category Write

Parameters 00 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/io-github-vmoranv-jshookmcp/adb-file-push.md

WHAT IT DOES

What adb_file_push does on Jshookmcp

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

RISK

Why adb_file_push is rated Medium

Uploads files to Android device; potential for malicious code injection or system compromise depending on target path and contents.

From the tool's definition Push a local file to an Android device

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs adb_file_push safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Jshookmcp, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For adb_file_push, this is the rule to start with:

adb_file_push Rate-limited

adb_file_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_file_push": {
      "limits": [
        {
          "counter": "adb_file_push_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Jshookmcp, apply this rule, and every adb_file_push call is checked against it from then on.

FAQ

Questions about adb_file_push

What does the adb_file_push tool do? +

Push a local file to an Android device using normal ADB permissions. It is categorised as a Write tool in the Jshookmcp 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_file_push? +

Register the Jshook MCP server in PolicyLayer and add a rule for adb_file_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 Jshookmcp. Nothing to install.

What risk level is adb_file_push? +

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

Can I rate-limit adb_file_push? +

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

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

adb_file_push is provided by the Jshook MCP server (@jshookmcp/jshook). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Jshook, and thousands of servers like it.

This server

All 736 Jshook tools →

Across the catalogue

write_file on 0sec → The MCP Attack Database →

Guides

Govern customer-ops agents →Argument validation →Scoped token →