High Risk →

sim_install

Install a .app bundle on a simulator (xcrun simctl install).

How to control sim_install ↓

What sim_install does on Claude Pascal MCP Server

AI agents invoke sim_install to trigger actions in Claude Pascal MCP Server. 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

Why sim_install needs a policy

This tool executes an xcrun simctl install command to install an application bundle on a simulator. It triggers an external system operation (running xcrun), and while it doesn't delete data, it modifies the simulator's state by installing potentially arbitrary application bundles.

From the tool's definition Install a .app bundle on a simulator (xcrun simctl install)

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

How to control sim_install

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

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

sim_install 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 Claude Pascal MCP Server — 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.

Related tools and policies

Go deeper

Questions about sim_install

What does the sim_install tool do? +

Install a .app bundle on a simulator (xcrun simctl install). It is categorised as a Execute tool in the Claude Pascal MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on sim_install? +

Register the Claude Pascal MCP Server MCP server in PolicyLayer and add a rule for sim_install: 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 Claude Pascal MCP Server. Nothing to install.

What risk level is sim_install? +

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

Can I rate-limit sim_install? +

Yes. Add a rate_limit block to the sim_install 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 sim_install completely? +

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

sim_install is provided by the Claude Pascal MCP Server MCP server (tina4stack/claude-pascal-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Claude Pascal MCP Server tool call.

Start from Claude Pascal MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

Free to start. No card required.

53 Claude Pascal MCP Server tools catalogued and risk-classified — across an index of 43,000+ 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.