Critical Risk →

reset_simulator

Reset a simulator by erasing all content and settings

How to control reset_simulator ↓

AI agents call reset_simulator to permanently remove resources in Xcode — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.

Critical Risk

Resetting a simulator erases all content and settings, which is an irreversible destructive action. While scoped to a development simulator rather than production data, the operation permanently removes all simulator state. This meets the Destructive category criteria as it cannot be undone.

From the tool's definition Tool description states 'Reset a simulator by erasing all content and settings' — this operation irreversibly wipes the simulator's state and cannot be undone.

Documented attack patterns abuse exactly the kind of access reset_simulator 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 reset_simulator:

policy.json
{
  "version": "1",
  "default": "deny",
  "hide": [
    "reset_simulator"
  ]
}

reset_simulator disappears from the agent's tool list entirely, and any attempt to call it is denied. The rest of the server keeps working.

  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.
RESTRICT THIS TOOL →

Free to start. No card required.

Go deeper

What does the reset_simulator tool do? +

Reset a simulator by erasing all content and settings. It is categorised as a Destructive tool in the Xcode MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.

How do I enforce a policy on reset_simulator? +

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

reset_simulator is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.

Can I rate-limit reset_simulator? +

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

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

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