bazel_ios_test

Run a Bazel iOS test target with simulator and test-output defaults.

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-test.md

WHAT IT DOES

What bazel_ios_test does on XcodeBazelMCP

AI agents invoke bazel_ios_test 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_test is rated High

This tool executes test targets via Bazel in a simulator environment. Running tests involves executing arbitrary code (the test binaries and their setups), which can have side effects depending on what the tests do. The blast radius is high because misconfigured or malicious test targets could execute harmful code on the host system or simulator environment.

From the tool's definition "Run a Bazel iOS test target with simulator and test-output defaults"

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs bazel_ios_test 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_test, this is the rule to start with:

bazel_ios_test Rate-limited

bazel_ios_test 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_test": {
      "limits": [
        {
          "counter": "bazel_ios_test_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_test call is checked against it from then on.

FAQ

Questions about bazel_ios_test

What does the bazel_ios_test tool do? +

Run a Bazel iOS test target with simulator and test-output defaults. 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_test? +

Register the XcodeBazel MCP server in PolicyLayer and add a rule for bazel_ios_test: 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_test? +

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

Can I rate-limit bazel_ios_test? +

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

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

bazel_ios_test 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

execute_test_case on Percepta MCP Server → All high-risk MCP tools → The MCP Attack Database →

Guides

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