High Risk →

install_app

Install an app on a simulator

How to control install_app ↓

AI agents invoke install_app to trigger actions in Xcode. 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.

High Risk

Installing an app on a simulator triggers an external operation (app installation) on a running simulator environment. It doesn't merely read or write data files, but actively deploys and registers an application on the simulator. Misuse could result in installing malicious or unauthorized apps onto simulator environments, but blast radius is limited to the local simulator context.

From the tool's definition Install an app on a simulator

Documented attack patterns abuse exactly the kind of access install_app gives an agent:

PolicyLayer is an MCP gateway — it sits between your AI agents and Xcode, and nothing reaches the server without passing your rules. This is the rule we recommend for install_app:

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "install_app": {
      "limits": [
        {
          "counter": "install_app_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

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

  1. Create a free account and register Xcode — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
RATE-LIMIT THIS TOOL →

Free to start. No card required.

Go deeper

What does the install_app tool do? +

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

How do I enforce a policy on install_app? +

Register the Xcode 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 Xcode. Nothing to install.

What risk level is install_app? +

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

Can I rate-limit install_app? +

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.

How do I block install_app completely? +

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.

What MCP server provides install_app? +

install_app is provided by the Xcode MCP server (xcode-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Xcode tool call.

Deterministic rules across all 69 Xcode tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

Free to start. No card required.

69 Xcode tools catalogued and risk-classified — across an index of 42,500+ MCP servers.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.