Executa comando adb shell em safe mode.
AI agents invoke adb_shell to trigger actions in AVD 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 enables execution of arbitrary shell commands on an Android Virtual Device through adb. While described as operating in 'safe mode', adb shell provides broad command execution capabilities that could be leveraged to install malware, exfiltrate data, modify system files, or compromise the development environment.
From the tool's definition Tool executes 'adb shell' commands with access to Android Virtual Device shell environment. Description states 'Executa comando adb shell em safe mode' (Executes adb shell command in safe mode).
Attacks that exploit this kind of access
Executa comando adb shell em safe mode. It is categorised as a Execute tool in the AVD MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the AVD MCP Server MCP server in PolicyLayer and add a rule for adb_shell: 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 AVD MCP Server. Nothing to install.
adb_shell 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_shell 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_shell. 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_shell is provided by the AVD MCP Server MCP server (jramalho/avd-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 →