adb_file_move
Move or rename a file/directory on the device. Moving FROM a system path is destructive — source depth protection refuses if source is at depth ≤ 1 from root. Symlinks resolved before checks. Cross-filesystem moves (e.g., /data → /sdcard) do a copy+delete internally and can be slow for large files.
This record as markdown: /tools/io-github-fullread-deepadb/adb-file-move.md
What adb_file_move does on Deepadb
AI agents call adb_file_move to permanently remove resources in Deepadb, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Why adb_file_move is rated Critical
Moving a file removes it from its original location (irreversible relocation), and cross-filesystem moves explicitly perform a copy+delete — the delete portion is irreversible. The tool itself acknowledges the destructive nature, especially when operating on system paths. Misuse by an AI agent could overwrite or permanently displace critical system or user files on the device.
From the tool's definition Move or rename a file/directory on the device. Moving FROM a system path is destructive — source depth protection refuses if source is at depth ≤ 1 from root. Cross-filesystem moves (e.g., /data → /sdcard) do a copy+delete internally.
Risk signalsAdmin/system-level operation
Attacks that exploit this kind of access
The rule that runs adb_file_move 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_move, this is the rule to start with:
adb_file_move is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.
The button opens the PolicyLayer dashboard: create your workspace, connect Deepadb, apply this rule, and every adb_file_move call is checked against it from then on.
Questions about adb_file_move
Move or rename a file/directory on the device. Moving FROM a system path is destructive — source depth protection refuses if source is at depth ≤ 1 from root. Symlinks resolved before checks. Cross-filesystem moves (e.g., /data → /sdcard) do a copy+delete internally and can be slow for large files. It is categorised as a Destructive tool in the Deepadb MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Deepadb MCP server in PolicyLayer and add a rule for adb_file_move: 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_move is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the adb_file_move 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_move. 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_move 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.
Across the catalogue