AI agents call device_list to retrieve information from uiautomator2 MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Device enumeration is a read operation that retrieves information about available devices without modifying, executing, or deleting anything. Even if misused by an AI agent, listing devices poses minimal risk—it cannot directly harm data or systems. The lack of a description slightly reduces confidence, but the naming convention and server purpose strongly indicate a read-only informational tool.
From the tool's definition Tool name is 'device_list' with no description provided. Based on sibling tools and server context (Android device automation via uiautomator2), this tool almost certainly lists connected/available Android devices, which is a read-only query operation with no…
Documented attack patterns abuse exactly the kind of access device_list gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and uiautomator2 MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for device_list:
{
"version": "1",
"default": "deny",
"tools": {
"device_list": {}
}
}device_list is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
device_list. It is categorised as a Read tool in the uiautomator2 MCP Server MCP Server, which means it retrieves data without modifying state.
Register the uiautomator2 MCP Server MCP server in PolicyLayer and add a rule for device_list: 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 uiautomator2 MCP Server. Nothing to install.
device_list 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 device_list 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 device_list. 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.
device_list is provided by the uiautomator2 MCP Server MCP server (tanbro/uiautomator2-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from uiautomator2 MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
77 uiautomator2 MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.