adb_file_copy
Copy a file or directory on the device. Pre-flight checks source size against destination available space. Post-verifies the copy by comparing file sizes. For recursive directory copies, use -r flag.
This record as markdown: /tools/io-github-fullread-deepadb/adb-file-copy.md
What adb_file_copy does on Deepadb
AI agents use adb_file_copy to create or update resources in Deepadb, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Deepadb environment.
Why adb_file_copy is rated Medium
This tool copies files and directories on an Android device, which modifies the device's filesystem. While the operation is reversible (files can be deleted afterward), the ability to copy arbitrary files could enable an agent to place malicious files, overwrite existing data, or exfiltrate sensitive data. The pre/post-flight checks mitigate some risk but do not eliminate the potential for misuse.
From the tool's definition "Copy a file or directory on the device" — the tool creates or modifies data on the target Android device by copying files/directories. The description indicates it performs reversible operations (copy, not delete) with pre-flight and post-verification checks.
Attacks that exploit this kind of access
The rule that runs adb_file_copy safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Deepadb, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For adb_file_copy, this is the rule to start with:
adb_file_copy 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.
The button opens the PolicyLayer dashboard: create your workspace, connect Deepadb, apply this rule, and every adb_file_copy call is checked against it from then on.
Questions about adb_file_copy
Copy a file or directory on the device. Pre-flight checks source size against destination available space. Post-verifies the copy by comparing file sizes. For recursive directory copies, use -r flag. It is categorised as a Write tool in the Deepadb MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Deepadb MCP server in PolicyLayer and add a rule for adb_file_copy: 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 Deepadb. Nothing to install.
adb_file_copy is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the adb_file_copy 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.
Set action: deny in the PolicyLayer policy for adb_file_copy. 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.
adb_file_copy is provided by the Deepadb MCP server (deepadb). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Deepadb, and thousands of servers like it.
This server
Across the catalogue