隐藏 Shizuku 小窗(缩到右上角极小尺寸 + force-stop App UI)。
AI agents invoke shizuku_hide 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 hides the Shizuku floating window by shrinking it and force-stopping the Shizuku App UI. Force-stopping an app process is an external system operation (Execute category). While it doesn't permanently delete data, it forcibly terminates a running process, which could disrupt ongoing operations. The severity is medium because it affects a specific system service (Shizuku) but is generally recoverable.
From the tool's definition force-stop App UI — triggers a force-stop of an application's UI process, which is an external system operation affecting running processes
Attacks that exploit this kind of access
隐藏 Shizuku 小窗(缩到右上角极小尺寸 + force-stop App UI)。. 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_hide: 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_hide 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_hide 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_hide. 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_hide 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 →