Unlock the device with password, PIN, pattern, or swipe. Pattern uses 3x3 grid numbered 0-8 (top-left to bottom-right), e.g.,
AI agents invoke adb_unlock to trigger actions in Openclaw Adb. 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 performs a security-sensitive action by unlocking an Android device using credentials (password, PIN, pattern, or swipe). It executes an ADB command that bypasses the device lock screen, which could expose all device data and functions to unauthorized access. It is classified as Execute because it triggers an external operation on a physical device; severity is high because misuse grants full device access.
From the tool's definition Unlock the device with password, PIN, pattern, or swipe
Attacks that exploit this kind of access
Unlock the device with password, PIN, pattern, or swipe. Pattern uses 3x3 grid numbered 0-8 (top-left to bottom-right), e.g.,. It is categorised as a Execute tool in the Openclaw Adb MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Openclaw Adb MCP server in PolicyLayer and add a rule for adb_unlock: 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 Openclaw Adb. Nothing to install.
adb_unlock 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_unlock 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_unlock. 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_unlock is provided by the Openclaw Adb MCP server (wilsonbeam/openclaw-adb-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →