xcode_record_simulator · Xcode MCP: Risk & Policy

WHAT IT DOES

What xcode_record_simulator does on Xcode

AI agents invoke xcode_record_simulator 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.

WHY IT NEEDS A POLICY

Why xcode_record_simulator needs a policy

Recording video of a simulator triggers an external operation (screen capture/recording) on the simulator. It has side effects (creates a video file) but primarily executes an action against the simulator environment. It's not purely destructive, financial, or a simple read/write of existing data.

From the tool's definition Record video of a simulator

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

xcode_record_simulator Rate-limited

xcode_record_simulator 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": {
    "xcode_record_simulator": {
      "limits": [
        {
          "counter": "xcode_record_simulator_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 Xcode, so you can run agents against it safely.

FAQ

Questions about xcode_record_simulator

What does the xcode_record_simulator tool do? +

Record video of 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 xcode_record_simulator? +

Register the Xcode MCP server in PolicyLayer and add a rule for xcode_record_simulator: 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 xcode_record_simulator? +

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

Can I rate-limit xcode_record_simulator? +

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

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

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