Launch an app by package name
AI agents invoke launch_app to trigger actions in Enhanced 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.
Launching an application triggers an external operation with effects that depend on which app is specified as an argument. This falls under Execute category because it runs/initiates a process on an Android device.
From the tool's definition Tool is named 'launch_app' and described as 'Launch an app by package name'. The sibling tools on this server (clear_app_data, clear_logcat, clear_proxy, check_flutter_app_running, double_tap, find_element_by_id) are all executable actions that trigger real…
Attacks that exploit this kind of access
Launch an app by package name. It is categorised as a Execute tool in the Enhanced ADB MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Enhanced ADB MCP Server MCP server in PolicyLayer and add a rule for launch_app: 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 Enhanced ADB MCP Server. Nothing to install.
launch_app 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 launch_app 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 launch_app. 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.
launch_app is provided by the Enhanced ADB MCP Server MCP server (rahulkr/r_adb_mcp_server). 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 →