simulator_install_app · Xclaude Plugin MCP: Risk & Policy

WHAT IT DOES

What simulator_install_app does on Xclaude Plugin

AI agents use simulator_install_app to create or update resources in Xclaude Plugin — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Xclaude Plugin environment.

WHY IT NEEDS A POLICY

Why simulator_install_app needs a policy

Installing an app on a simulator creates new data/state on the device but is reversible (the app can be uninstalled). This is a Write operation — it modifies the simulator's state by adding a new application, but does not execute arbitrary code or irreversibly destroy data.

From the tool's definition Install app on simulator

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

simulator_install_app Rate-limited

simulator_install_app stays usable, but capped — an agent stuck in a loop can't make hundreds of changes 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_install_app": {
      "limits": [
        {
          "counter": "simulator_install_app_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

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_install_app

What does the simulator_install_app tool do? +

Install app on simulator. It is categorised as a Write tool in the Xclaude Plugin MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on simulator_install_app? +

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

What risk level is simulator_install_app? +

simulator_install_app is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit simulator_install_app? +

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

How do I block simulator_install_app completely? +

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

What MCP server provides simulator_install_app? +

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

// THE FULL RECORD

simulator_install_app is one line of Xclaude Plugin's registry record.

The record carries the whole server: verified identity, auth posture, risk grade, every tool classified, recommended policy — re-checked continuously.

Teams ship this data inside their own products. See what a licence covers →