simulator_create · Xclaude Plugin MCP: Risk & Policy

WHAT IT DOES

What simulator_create does on Xclaude Plugin

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

WHY IT NEEDS A POLICY

Why simulator_create needs a policy

This tool creates a new resource (simulator device) which is a reversible write operation—simulators can be deleted or reconfigured. It does not execute arbitrary code on the target application, delete existing data, move funds, or trigger irreversible changes to production systems.

From the tool's definition Tool description states 'Create a new simulator device', indicating data creation in the iOS simulator environment. Context shows this is part of an iOS development toolset (Xcode/IDB tools) that manages simulator lifecycle.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

simulator_create Rate-limited

simulator_create 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": {
    "simulator_create": {
      "limits": [
        {
          "counter": "simulator_create_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 Xclaude Plugin, so you can run agents against it safely.

FAQ

Questions about simulator_create

What does the simulator_create tool do? +

Create a new simulator device. It is categorised as a Write tool in the Xclaude Plugin MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on simulator_create? +

Register the Xclaude Plugin MCP server in PolicyLayer and add a rule for simulator_create: 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 Xclaude Plugin. Nothing to install.

What risk level is simulator_create? +

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

Can I rate-limit simulator_create? +

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

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

simulator_create is provided by the Xclaude Plugin MCP server (conorluddy/xclaude-plugin). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.