Get detailed information about a connected iOS device including model, iOS version, battery, storage, etc.
AI agents call device_info 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.
device_info is purely informational—it queries and returns device metadata (hardware model, OS version, battery status, storage capacity) with no capability to modify, execute, or delete. This is a non-destructive retrieval operation, making it a Read category tool.
From the tool's definition Tool retrieves detailed information about a connected iOS device including model, iOS version, battery, storage, etc. The description explicitly indicates read-only operations that query device state without modification or side effects.
Attacks that exploit this kind of access
Get detailed information about a connected iOS device including model, iOS version, battery, storage, etc. 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 device_info: 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.
device_info 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_info 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_info. 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_info 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 →