bazel_ios_health
Check local Bazel, Xcode, simulator, and workspace readiness for iOS Bazel builds.
This record as markdown: /tools/xcodebazelmcp-xcodebazelmcp/bazel-ios-health.md
What bazel_ios_health does on XcodeBazelMCP
AI agents call bazel_ios_health to retrieve information from XcodeBazelMCP without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why bazel_ios_health is rated Low
This tool performs health checks and diagnostics on the build environment (Bazel, Xcode, simulator, workspace state). It retrieves status information and validates readiness without modifying, executing operations, or deleting data. The blast radius of misuse is minimal—incorrect health assessment would merely provide false information to the user, not cause harm.
From the tool's definition Tool name 'bazel_ios_health' with description 'Check local Bazel, Xcode, simulator, and workspace readiness' — the verb 'check' and 'readiness' inspection indicate querying/diagnostic operations with no side effects.
Attacks that exploit this kind of access
The rule that runs bazel_ios_health 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_health, this is the rule to start with:
bazel_ios_health is read-only, so it stays allowed. 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_ios_health call is checked against it from then on.
Questions about bazel_ios_health
Check local Bazel, Xcode, simulator, and workspace readiness for iOS Bazel builds. It is categorised as a Read tool in the XcodeBazelMCP MCP Server, which means it retrieves data without modifying state.
Register the XcodeBazel MCP server in PolicyLayer and add a rule for bazel_ios_health: 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_ios_health is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the bazel_ios_health 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_ios_health. 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_ios_health 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.
This server
Across the catalogue