boot_device · React Native Dev MCP: Risk & Policy

WHAT IT DOES

What boot_device does on React Native Dev

AI agents invoke boot_device 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.

WHY IT NEEDS A POLICY

Why boot_device needs a policy

This tool starts/boots a simulator or emulator, which is an external system operation that triggers device initialization. It is not simply reading data, nor is it destructive or financial. It executes an external operation (launching a virtual device), making Execute the appropriate category. Misuse could consume system resources or interfere with other development workflows.

From the tool's definition Boot a simulator/emulator by id and wait until it is usable

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

boot_device Rate-limited

boot_device stays usable, but rate-capped — a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "boot_device": {
      "limits": [
        {
          "counter": "boot_device_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches React Native Dev, so you can run agents against it safely.

FAQ

Questions about boot_device

What does the boot_device tool do? +

Boot a simulator/emulator by id and wait until it is usable. No-op if already booted. For cold Android AVDs use the avd:<name> id from list_devices. 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.

How do I enforce a policy on boot_device? +

Register the React Native Dev MCP server in PolicyLayer and add a rule for boot_device: 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.

What risk level is boot_device? +

boot_device is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit boot_device? +

Yes. Add a rate_limit block to the boot_device 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.

How do I block boot_device completely? +

Set action: deny in the PolicyLayer policy for boot_device. 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.

What MCP server provides boot_device? +

boot_device 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.