bazel_visionos_build

What bazel_visionos_build does on XcodeBazelMCP

AI agents invoke bazel_visionos_build 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.

Why bazel_visionos_build is rated High

This tool invokes the Bazel build system to compile and link visionOS applications. While nominally productive, builds are Execute-category actions because they trigger external processes whose actual effects depend on build configuration and target specification. An agent with this tool could compile malicious code, invoke build scripts with side effects, or generate artifacts that affect downstream systems.

From the tool's definition Tool performs 'Build a Bazel visionOS target', which triggers compilation and linking operations via the Bazel build system. Building is an external operation whose effects (binary artifacts, potential side effects) depend on the target arguments provided.

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

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

Questions about bazel_visionos_build