查看 Shizuku 的运行状态：App 进程、shizuku_server 守护进程、rish 可用性。
AI agents call shizuku_status to retrieve information from Android MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries and returns status information about Shizuku components (app process, daemon, availability). It performs read-only introspection with no side effects. However, severity is elevated to medium because Shizuku is a privileged service framework that can grant elevated permissions to apps - information about its status could be reconnaissance data useful for privilege escalation attacks, even though the…
From the tool's definition 查看 Shizuku 的运行状态 (View Shizuku running status) - retrieves status information about App process, shizuku_server daemon, and rish availability without modifying state.
Attacks that exploit this kind of access
查看 Shizuku 的运行状态：App 进程、shizuku_server 守护进程、rish 可用性。. It is categorised as a Read tool in the Android MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Android MCP Server MCP server in PolicyLayer and add a rule for shizuku_status: 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_status is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the shizuku_status 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_status. 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_status 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 →