AI agents call xcode_erase_simulator to permanently remove resources in MCP Appium Server — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Erasing a simulator is a destructive operation that cannot be undone. All data stored on the simulator is permanently removed. This is categorized as Destructive rather than Execute because the operation is inherently irreversible and destructive in nature. The severity is high because an AI agent misusing this could destroy critical test environments, development data, or simulator state without recovery options.
From the tool's definition Tool name 'xcode_erase_simulator' and description 'Erase all data from a simulator' explicitly indicate irreversible deletion of simulator data.
Risk signalsBulk/mass operation — affects multiple targets
Documented attack patterns abuse exactly the kind of access xcode_erase_simulator gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and MCP Appium Server, and nothing reaches the server without passing your rules. This is the rule we recommend for xcode_erase_simulator:
{
"version": "1",
"default": "deny",
"hide": [
"xcode_erase_simulator"
]
}xcode_erase_simulator disappears from the agent's tool list entirely, and any attempt to call it is denied. The rest of the server keeps working.
Free to start. No card required.
Erase all data from a simulator. It is categorised as a Destructive tool in the MCP Appium Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the MCP Appium Server MCP server in PolicyLayer and add a rule for xcode_erase_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 MCP Appium Server. Nothing to install.
xcode_erase_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_erase_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_erase_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_erase_simulator is provided by the MCP Appium Server MCP server (rahulec08/appium-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 110 MCP Appium Server tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
110 MCP Appium Server tools catalogued and risk-classified — across an index of 42,500+ MCP servers.