set_simulator_location · Sl Test MCP: Risk & Policy

WHAT IT DOES

What set_simulator_location does on Sl Test

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

WHY IT NEEDS A POLICY

Why set_simulator_location needs a policy

This tool modifies the simulator's GPS location state. It's a Write operation (reversible configuration change) with low severity since it only affects a local simulator environment, not production data or real systems.

From the tool's definition Sets a custom GPS location for the simulator

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

set_simulator_location Rate-limited

set_simulator_location 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": {
    "set_simulator_location": {
      "limits": [
        {
          "counter": "set_simulator_location_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 Sl Test, so you can run agents against it safely.

FAQ

Questions about set_simulator_location

What does the set_simulator_location tool do? +

Sets a custom GPS location for the simulator. It is categorised as a Write tool in the Sl Test MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on set_simulator_location? +

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

What risk level is set_simulator_location? +

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

Can I rate-limit set_simulator_location? +

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

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

set_simulator_location is provided by the Sl Test MCP server (sampsonky/xcodebuildmcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.