Create a full backup of device data using ADB backup.
AI agents invoke adb_backup_device to trigger actions in Android Forensics ADB MCP Server. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.
This tool executes an ADB backup command on an external device, which is an active operation that reads and transfers potentially sensitive personal data off a device. It is not purely Read (it runs an external command via ADB that has side effects on both the device and local storage), and it is not Destructive or Financial.
From the tool's definition 'Create a full backup of device data using ADB backup' — triggers an ADB backup operation on a connected Android device
Documented attack patterns abuse exactly the kind of access adb_backup_device gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Android Forensics ADB MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for adb_backup_device:
{
"version": "1",
"default": "deny",
"tools": {
"adb_backup_device": {
"limits": [
{
"counter": "adb_backup_device_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
}adb_backup_device stays usable, but rate-capped — a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Create a full backup of device data using ADB backup. It is categorised as a Execute tool in the Android Forensics ADB MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Android Forensics ADB MCP Server MCP server in PolicyLayer and add a rule for adb_backup_device: 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 Android Forensics ADB MCP Server. Nothing to install.
adb_backup_device is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the adb_backup_device 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_backup_device. 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_backup_device is provided by the Android Forensics ADB MCP Server MCP server (0x-professor/droidforensics-suite). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Android Forensics ADB MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
58 Android Forensics ADB MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.