bazel_ios_set_simulator_appearance

Set the simulator UI appearance to light or dark mode.

SERVERXcodeBazelMCP SOURCExcodebazelmcp/xcodebazelmcp

High RISK CLASS

Category Execute

Parameters 00 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/xcodebazelmcp-xcodebazelmcp/bazel-ios-set-simulator-appearance.md

WHAT IT DOES

What bazel_ios_set_simulator_appearance does on XcodeBazelMCP

AI agents invoke bazel_ios_set_simulator_appearance to trigger actions in XcodeBazelMCP. 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.

RISK

Why bazel_ios_set_simulator_appearance is rated High

This tool triggers an external operation on a simulator (changing its UI appearance setting). It's not a simple read, nor does it create/modify persistent data in a reversible write sense — it executes a state change on a running simulator process. The blast radius is low since it only affects the simulator's visual appearance setting.

From the tool's definition Set the simulator UI appearance to light or dark mode

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs bazel_ios_set_simulator_appearance safely

PolicyLayer is an MCP gateway: it sits between your AI agents and XcodeBazelMCP, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For bazel_ios_set_simulator_appearance, this is the rule to start with:

bazel_ios_set_simulator_appearance Rate-limited

bazel_ios_set_simulator_appearance 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": {
    "bazel_ios_set_simulator_appearance": {
      "limits": [
        {
          "counter": "bazel_ios_set_simulator_appearance_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect XcodeBazelMCP, apply this rule, and every bazel_ios_set_simulator_appearance call is checked against it from then on.

FAQ

Questions about bazel_ios_set_simulator_appearance

What does the bazel_ios_set_simulator_appearance tool do? +

Set the simulator UI appearance to light or dark mode. It is categorised as a Execute tool in the XcodeBazelMCP MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on bazel_ios_set_simulator_appearance? +

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

What risk level is bazel_ios_set_simulator_appearance? +

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

Can I rate-limit bazel_ios_set_simulator_appearance? +

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

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

bazel_ios_set_simulator_appearance is provided by the XcodeBazel MCP server (xcodebazelmcp/xcodebazelmcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on XcodeBazel, and thousands of servers like it.

This server

All 125 XcodeBazel tools → High-risk tools on this server →

Across the catalogue

set_breakpoint on Frida Game Hacking MCP → All high-risk MCP tools → The MCP Attack Database →

Guides

Govern code and CI agents →Agent sandbox →Least privilege for MCP →