Reset a simulator to factory state (erase content and settings)
AI agents call xcode_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.
This tool irreversibly deletes all content and settings on a simulator, which cannot be undone. While the impact is scoped to a development simulator rather than production systems, it still constitutes permanent data loss. An AI agent misusing this could destroy development environments, lose work-in-progress test data, or disrupt team workflows.
From the tool's definition Reset a simulator to factory state (erase content and settings) - the words 'erase' and 'factory state' indicate irreversible deletion of simulator data and configurations.
Attacks that exploit this kind of access
Reset a simulator to factory state (erase 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.
Register the Xcode MCP server in PolicyLayer and add a rule for xcode_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.
xcode_reset_simulator is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the xcode_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.
Set action: deny in the PolicyLayer policy for xcode_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.
xcode_reset_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.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →