Install an APK file into the Gbox Android box.
AI agents invoke install_apk to trigger actions in Android Tester MCP. 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.
Installing an APK onto a device is an execution-level operation that deploys software onto the system. It can introduce malicious code, change device behavior, or enable further exploitation. It is not merely a write operation because it triggers OS-level installation processes and executes package installers, making it an Execute-category action with high severity due to the potential for arbitrary code deployment.
From the tool's definition Install an APK file into the Gbox Android box
Attacks that exploit this kind of access
Install an APK file into the Gbox Android box. It is categorised as a Execute tool in the Android Tester MCP MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Android Tester MCP server in PolicyLayer and add a rule for install_apk: 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 Android Tester MCP. Nothing to install.
install_apk 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 install_apk 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 install_apk. 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.
install_apk is provided by the Android Tester MCP server (zhenweiwang1990/android-tester-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 →