显示/启动 Shizuku App 窗口。
AI agents invoke shizuku_show to trigger actions in Android 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.
The tool starts/launches the Shizuku app, which is a privileged Android service that grants elevated API access to other apps. Launching it constitutes an external operation on the device. Shizuku itself enables high-privilege operations, so starting it could be a precursor to privileged actions, but the tool itself is classified as Execute (triggering an app launch).
From the tool's definition 显示/启动 Shizuku App 窗口 — launches/starts the Shizuku application window, triggering an external operation on the Android device
Attacks that exploit this kind of access
显示/启动 Shizuku App 窗口。. It is categorised as a Execute tool in the Android MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Android MCP Server MCP server in PolicyLayer and add a rule for shizuku_show: 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 MCP Server. Nothing to install.
shizuku_show 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 shizuku_show 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 shizuku_show. 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.
shizuku_show is provided by the Android MCP Server MCP server (wujie272/android-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 →