simulator_launch_app · Xclaude Plugin MCP: Risk & Policy

WHAT IT DOES

What simulator_launch_app does on Xclaude Plugin

AI agents invoke simulator_launch_app to trigger actions in Xclaude Plugin. 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 simulator_launch_app needs a policy

This tool triggers execution of an application within an iOS simulator environment. While not destructive or financial, launching an arbitrary app is an Execute category action because it runs external code/processes and could have unintended side effects depending on which app is launched (e.g., making network calls, modifying simulator state, accessing sensitive data).

From the tool's definition 'Launch app on simulator' - this tool executes an action (launching an application) on a simulated iOS device, which is an external operation whose effects depend on which app is specified as an argument.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

simulator_launch_app Rate-limited

simulator_launch_app 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": {
    "simulator_launch_app": {
      "limits": [
        {
          "counter": "simulator_launch_app_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 Xclaude Plugin, so you can run agents against it safely.

FAQ

Questions about simulator_launch_app

What does the simulator_launch_app tool do? +

Launch app on simulator. It is categorised as a Execute tool in the Xclaude Plugin MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on simulator_launch_app? +

Register the Xclaude Plugin MCP server in PolicyLayer and add a rule for simulator_launch_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 Xclaude Plugin. Nothing to install.

What risk level is simulator_launch_app? +

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

Can I rate-limit simulator_launch_app? +

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

How do I block simulator_launch_app completely? +

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

What MCP server provides simulator_launch_app? +

simulator_launch_app is provided by the Xclaude Plugin MCP server (conorluddy/xclaude-plugin). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.