bazel_macos_test

THE RISK

High Risk

Why bazel_macos_test needs a policy

This tool executes test code on the macOS platform via Bazel. Running tests executes arbitrary code (the test targets and their dependencies), which can have side effects depending on what the tests do. The blast radius is high because arbitrary code execution could affect the local system, file system, or external services.

From the tool's definition Run a Bazel macOS unit test target (macos_unit_test)

Documented attack patterns abuse exactly the kind of access bazel_macos_test gives an agent:

POLICY

How to control bazel_macos_test

PolicyLayer is an MCP gateway — it sits between your AI agents and XcodeBazelMCP, and nothing reaches the server without passing your rules. This is the rule we recommend for bazel_macos_test:

policy.json

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

bazel_macos_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.

Create a free account and register XcodeBazelMCP — nothing to install.
Add this policy — paste it, or build it visually.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

RATE-LIMIT THIS TOOL →

Free to start. No card required.

EXPLORE

Related tools and policies

More XcodeBazelMCP tools

Destructive bazel_ios_agent_debug_log_clear Delete an agent debug NDJSON log file before a repro run (Cursor debug mode). Safe no-op i Destructive bazel_ios_clean Clean Bazel build outputs. Use expunge to remove the entire output base. Destructive bazel_ios_erase_simulator Erase all content and settings from a simulator, restoring it to factory state. Destructive swift_package_clean Clean build artifacts of a Swift package ( Destructive bazel_ios_device_unpair Unpair a previously paired physical iOS device. Execute bazel_ios_agent_debug_repro One-shot Cursor debug repro: clear host log → build_and_run with AGENT_DEBUG_ launchEnv → Execute bazel_ios_lldb_breakpoint Set a breakpoint by file+line, symbol name, or delete/list breakpoints. Execute bazel_ios_privacy Grant, revoke, or reset privacy permissions for an app on a simulator.

All 117 XcodeBazelMCP tools →

Execute tools on other servers

Android Forensics ADB MCP Server adb_shell_command EMBA-MCP run_emba_scan Frida Game Hacking MCP remove_breakpoint Procmon request_elevation

Go deeper

High-risk tools in XcodeBazelMCP → Every high-risk tool this server exposes, in one view.
All high-risk MCP tools → Every high-risk tool across the catalogue, and the policy pattern that contains them.
The MCP Attack Database → Documented attack patterns against MCP deployments — and the policies that stop them.
Agent sandbox → Bounding what an agent can execute and where the boundary should sit.
Least privilege for MCP → Granting agents the minimum tool surface the task needs.
Rate Limiting MCP Tool Calls: A Practical Guide →
MCP Security: Why Prompt Guardrails Aren't Enough →

FAQ

Questions about bazel_macos_test

What does the bazel_macos_test tool do? +

Run a Bazel macOS unit test target (macos_unit_test). 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_macos_test? +

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

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

Can I rate-limit bazel_macos_test? +

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

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

bazel_macos_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.

Enforce policy on every XcodeBazelMCP tool call.

Start from XcodeBazelMCP, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

CHECK YOUR STACK →