bazel_watchos_build
Build a Bazel watchOS target (watchos_application, watchos_extension, etc.).
This record as markdown: /tools/xcodebazelmcp-xcodebazelmcp/bazel-watchos-build.md
What bazel_watchos_build does on XcodeBazelMCP
AI agents invoke bazel_watchos_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_watchos_build is rated High
This tool executes a build operation against a Bazel target. While building itself is typically considered a normal development operation, classifying it as Execute reflects that: (1) it runs an external build system with complex side effects, (2) the outcome depends on specified build arguments, (3) it generates artifacts and modifies build cache state, and (4) in the context of an AI agent with unvetted access, it…
From the tool's definition Tool performs 'Build a Bazel watchOS target' — invokes the Bazel build system to compile code, which is an external operation whose effects depend on build arguments and target specification.
Attacks that exploit this kind of access
The rule that runs bazel_watchos_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_watchos_build, this is the rule to start with:
bazel_watchos_build 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.
The button opens the PolicyLayer dashboard: create your workspace, connect XcodeBazelMCP, apply this rule, and every bazel_watchos_build call is checked against it from then on.
Questions about bazel_watchos_build
Build a Bazel watchOS target (watchos_application, watchos_extension, etc.). 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.
Register the XcodeBazel MCP server in PolicyLayer and add a rule for bazel_watchos_build: 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.
bazel_watchos_build is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the bazel_watchos_build 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.
Set action: deny in the PolicyLayer policy for bazel_watchos_build. 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.
bazel_watchos_build 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.
More on XcodeBazel, and thousands of servers like it.
Across the catalogue