List all installed applications on the iOS device.
AI agents call list_apps 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 queries and returns information about installed applications on a device without modifying, executing, or deleting anything. It is a read-only operation that retrieves device state. The blast radius is minimal—an AI agent misusing this would only expose what apps are installed, which is low-sensitivity metadata on a developer's device.
From the tool's definition Tool name 'list_apps' and description 'List all installed applications on the iOS device' indicate data retrieval with no side effects.
Attacks that exploit this kind of access
List all installed applications on the iOS device. 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_apps: 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_apps 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_apps 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_apps. 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_apps 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 →