List all connected iOS devices. Returns device names, UDIDs, and connection info.
AI agents call list_devices to retrieve information from Expo Dev Build MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and queries information about connected devices without performing any side effects, modifications, or code execution. It is a straightforward information-gathering operation that falls squarely into the Read category. The severity is low because the blast radius of misuse (an attacker learning what devices are connected) is limited in scope and does not enable further damaging actions on its own.
From the tool's definition Tool name 'list_devices' and description 'List all connected iOS devices. Returns device names, UDIDs, and connection info.' indicate pure retrieval of device enumeration data with no modification or execution.
Attacks that exploit this kind of access
List all connected iOS devices. Returns device names, UDIDs, and connection info. It is categorised as a Read tool in the Expo Dev Build MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Expo Dev Build MCP Server MCP server in PolicyLayer and add a rule for list_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 Expo Dev Build MCP Server. Nothing to install.
list_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 list_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 list_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.
list_devices is provided by the Expo Dev Build MCP Server MCP server (ryan-crabbe/expo-dev-build-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 →