bazel_macos_log
Stream system logs on macOS, optionally filtered by process.
This record as markdown: /tools/xcodebazelmcp-xcodebazelmcp/bazel-macos-log.md
What bazel_macos_log does on XcodeBazelMCP
AI agents call bazel_macos_log 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_macos_log is rated Low
This tool retrieves and streams existing system logs without creating, modifying, deleting, or executing any operations. Filtering by process is a read-only query operation. While logs may contain sensitive information, the tool itself performs no side effects—it simply accesses already-generated diagnostic data.
From the tool's definition Tool name 'bazel_macos_log' and description 'Stream system logs on macOS, optionally filtered by process' indicates reading/querying existing log data with no modification or deletion capability.
Attacks that exploit this kind of access
The rule that runs bazel_macos_log 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_log, this is the rule to start with:
bazel_macos_log 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_macos_log call is checked against it from then on.
Questions about bazel_macos_log
Stream system logs on macOS, optionally filtered by process. 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_macos_log: 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_log 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_macos_log 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_log. 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_log 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