bazel_macos_coverage
Run Bazel macOS test with coverage collection and lcov output.
This record as markdown: /tools/xcodebazelmcp-xcodebazelmcp/bazel-macos-coverage.md
What bazel_macos_coverage does on XcodeBazelMCP
AI agents invoke bazel_macos_coverage 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_macos_coverage is rated High
This is an Execute category tool because it triggers the execution of tests via Bazel, which runs code on the system. While the immediate output (coverage/lcov data) is non-destructive, the tool executes arbitrary test code whose side effects depend on test arguments and system state. It is not Destructive because coverage collection itself does not permanently delete or overwrite data.
From the tool's definition The tool 'bazel_macos_coverage' runs Bazel macOS tests with coverage collection and lcov output. The verb 'run' combined with 'test' indicates code execution.
Attacks that exploit this kind of access
The rule that runs bazel_macos_coverage 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_macos_coverage, this is the rule to start with:
bazel_macos_coverage 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_macos_coverage call is checked against it from then on.
Questions about bazel_macos_coverage
Run Bazel macOS test with coverage collection and lcov output. 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_macos_coverage: 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_macos_coverage 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_macos_coverage 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_macos_coverage. 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_macos_coverage 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