Launch a specific activity
AI agents invoke launch_activity 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 activity on an Android device executes arbitrary application code whose behavior depends on which activity is specified. This is a side-effect-causing operation that triggers external code execution (the activity itself), classifying it as Execute rather than Read or Write.
From the tool's definition Tool name 'launch_activity' combined with description 'Launch a specific activity' indicates execution of an Android activity, which is a runtime operation that triggers code execution on the device.
Attacks that exploit this kind of access
Launch a specific activity. 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_activity: 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_activity 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_activity 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_activity. 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_activity 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 →