bazel_macos_bundle_id
Read the CFBundleIdentifier from a macOS .app bundle.
This record as markdown: /tools/xcodebazelmcp-xcodebazelmcp/bazel-macos-bundle-id.md
What bazel_macos_bundle_id does on XcodeBazelMCP
AI agents call bazel_macos_bundle_id 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_bundle_id is rated Low
This tool retrieves metadata (the CFBundleIdentifier) from an existing macOS application bundle. It performs a query operation that returns information without modifying, executing, or deleting anything. The only potential risk is disclosure of application identifiers, which is low severity in most contexts. The capability is explicitly scoped to reading a specific property from a bundle file.
From the tool's definition Tool name and description: 'Read the CFBundleIdentifier from a macOS .app bundle.' The verb 'Read' combined with the operation of querying/retrieving a bundle identifier from an existing app bundle indicates a read-only information retrieval operation with no…
Attacks that exploit this kind of access
The rule that runs bazel_macos_bundle_id 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_bundle_id, this is the rule to start with:
bazel_macos_bundle_id 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_bundle_id call is checked against it from then on.
Questions about bazel_macos_bundle_id
Read the CFBundleIdentifier from a macOS .app bundle. 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_bundle_id: 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_bundle_id 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_bundle_id 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_bundle_id. 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_bundle_id 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