xcode_set_simulator_location · Xcode MCP: Risk & Policy

WHAT IT DOES

What xcode_set_simulator_location does on Xcode

AI agents invoke xcode_set_simulator_location 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_set_simulator_location needs a policy

This tool modifies the state of a running simulator by changing its simulated GPS/location data. It is an external operation affecting a simulator process, not a simple data read or write to a file/database. Misuse has low blast radius as it only affects simulated location in a development environment and is reversible.

From the tool's definition 'Set the simulated location for a simulator' — triggers an external operation on a running simulator instance

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

xcode_set_simulator_location Rate-limited

xcode_set_simulator_location 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_set_simulator_location": {
      "limits": [
        {
          "counter": "xcode_set_simulator_location_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_set_simulator_location

What does the xcode_set_simulator_location tool do? +

Set the simulated location for 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_set_simulator_location? +

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

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

Can I rate-limit xcode_set_simulator_location? +

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

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

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