simctl_boot_device · Simctl MCP: Risk & Policy

WHAT IT DOES

What simctl_boot_device does on Simctl

AI agents invoke simctl_boot_device to trigger actions in Simctl. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.

WHY IT NEEDS A POLICY

Why simctl_boot_device needs a policy

Booting a simulator is an external operation that starts a process/VM-like environment. It is not a simple data read or write, nor is it destructive or financial. It falls under Execute as it triggers an operation in the OS/simulator runtime.

From the tool's definition 'Boot a simulator device' — triggers an external system operation (starting a simulator process) whose effects depend on the device argument.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

simctl_boot_device Rate-limited

simctl_boot_device stays usable, but rate-capped — a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "simctl_boot_device": {
      "limits": [
        {
          "counter": "simctl_boot_device_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Simctl, so you can run agents against it safely.

FAQ

Questions about simctl_boot_device

What does the simctl_boot_device tool do? +

Boot a simulator device. It is categorised as a Execute tool in the Simctl MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on simctl_boot_device? +

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

What risk level is simctl_boot_device? +

simctl_boot_device is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit simctl_boot_device? +

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

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

simctl_boot_device is provided by the Simctl MCP server (nzrsky/simctl-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.