Install a built app artifact on a booted device: a .app bundle (iOS simulator) or .apk (Android). Returns the app id for launch_app.
AI agents invoke install_app to trigger actions in React Native Dev. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.
Installing an application on a device is an external operation that modifies the device state by deploying software. It is not a simple data write (reversible record creation) but rather triggers an OS-level installation process with side effects. It could also be used to install malicious apps, giving it medium severity.
From the tool's definition Install a built app artifact on a booted device: a .app bundle (iOS simulator) or .apk (Android)
Attacks that exploit this kind of access
Install a built app artifact on a booted device: a .app bundle (iOS simulator) or .apk (Android). Returns the app id for launch_app. It is categorised as a Execute tool in the React Native Dev MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the React Native Dev MCP server in PolicyLayer and add a rule for install_app: 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 React Native Dev. Nothing to install.
install_app is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the install_app 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 install_app. 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.
install_app is provided by the React Native Dev MCP server (luizhbesper/react-native-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 →