AI agents invoke press_app_switch to trigger actions in 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 executes a device input action (pressing the app switcher/recents button) via ADB. It is an Execute category action as it triggers an external operation on the device. The blast radius is low since it only opens the recent apps UI and does not modify data or cause destructive effects.
From the tool's definition 按下应用切换键（多任务键） — triggers a hardware key press (app switch/multitask button) on the Android device
Documented attack patterns abuse exactly the kind of access press_app_switch gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Adb, and nothing reaches the server without passing your rules. This is the rule we recommend for press_app_switch:
{
"version": "1",
"default": "deny",
"tools": {
"press_app_switch": {
"limits": [
{
"counter": "press_app_switch_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
}press_app_switch 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.
按下应用切换键（多任务键）. It is categorised as a Execute tool in the Adb MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Adb MCP server in PolicyLayer and add a rule for press_app_switch: 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 Adb. Nothing to install.
press_app_switch 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 press_app_switch 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 press_app_switch. 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.
press_app_switch is provided by the Adb MCP server (wolfcoming/adb_mcp_server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Adb, 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.
48 Adb tools catalogued and risk-classified — across an index of 43,000+ MCP servers.