Get list of connected Android devices
AI agents call get_devices to retrieve information from MCP Emulator Controller without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool performs a read-only operation that lists connected Android devices. It has no side effects, does not modify data, execute code, destroy resources, or move financial assets. It is purely informational retrieval, placing it firmly in the Read category with low severity since disclosure of device list information poses minimal risk to confidentiality, integrity, or availability.
From the tool's definition Tool name and description indicate a query operation: 'Get list of connected Android devices' retrieves device information without modifying or executing actions on those devices.
Attacks that exploit this kind of access
Get list of connected Android devices. It is categorised as a Read tool in the MCP Emulator Controller MCP Server, which means it retrieves data without modifying state.
Register the MCP Emulator Controller MCP server in PolicyLayer and add a rule for get_devices: 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 MCP Emulator Controller. Nothing to install.
get_devices 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 get_devices 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 get_devices. 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.
get_devices is provided by the MCP Emulator Controller MCP server (teemo4621/mcp-emulator-controller). 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 →