MCP Tool Reference High Risk

boot_simulator

Boot an iOS simulator

Part of the Appium MCP server. Enforce policies on this tool with Intercept, the open-source MCP proxy.

appium-mcp Execute

WHEN AI AGENTS USE THIS TOOL

AI agents invoke boot_simulator to trigger processes or run actions in Appium. Execute operations can have side effects beyond the immediate call — triggering builds, sending notifications, or starting workflows. Rate limits and argument validation are essential to prevent runaway execution.

WHY ENFORCE A POLICY ON BOOT_SIMULATOR

boot_simulator can trigger processes with real-world consequences. An uncontrolled agent might start dozens of builds, send mass notifications, or kick off expensive compute jobs. Intercept enforces rate limits and validates arguments to keep execution within safe bounds.

RECOMMENDED POLICY

Execute tools trigger processes. Rate-limit and validate arguments to prevent unintended side effects.

appium.yaml
tools:
  boot_simulator:
    rules:
      - action: allow
        rate_limit:
          max: 10
          window: 60
        validate:
          required_args: true

See the full Appium policy for all 27 tools.

DETAILS

Tool Name

boot_simulator

Category

Execute

MCP Server

Appium MCP Server

Risk Level

High

MORE APPIUM TOOLS

View all 27 tools →

SIMILAR EXECUTE TOOLS ON OTHER SERVERS

RELATED READING

FREQUENTLY ASKED QUESTIONS

What does the boot_simulator tool do?

Boot an iOS simulator. It is categorised as a Execute tool in the Appium 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_simulator?

Add a rule in your Intercept YAML policy under the tools section for boot_simulator. You can allow, deny, rate-limit, or validate arguments. Then run Intercept as a proxy in front of the Appium MCP server.

What risk level is boot_simulator?

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

Can I rate-limit boot_simulator?

Yes. Add a rate_limit block to the boot_simulator rule in your Intercept 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_simulator completely?

Set action: deny in the Intercept policy for boot_simulator. 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_simulator?

boot_simulator is provided by the Appium MCP server (appium-mcp). Intercept sits as a proxy in front of this server to enforce policies before tool calls reach the server.

ENFORCE POLICIES ON APPIUM

Open source. One binary. Zero dependencies.