AI agents use xcode_create_simulator to create or update resources in MCP Appium Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your MCP Appium Server environment.
This tool creates a new iOS simulator instance, which is a reversible write operation (simulators can be deleted). It does not execute code or destructively modify existing data, but it does create a new resource on the system.
From the tool's definition Create a new iOS simulator
Documented attack patterns abuse exactly the kind of access xcode_create_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_create_simulator:
{
"version": "1",
"default": "deny",
"tools": {
"xcode_create_simulator": {
"limits": [
{
"counter": "xcode_create_simulator_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}xcode_create_simulator 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.
Free to start. No card required.
Create a new iOS simulator. It is categorised as a Write tool in the MCP Appium Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the MCP Appium Server MCP server in PolicyLayer and add a rule for xcode_create_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_create_simulator is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the xcode_create_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_create_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_create_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.