Extract CFBundleIdentifier from a built .app bundle.
AI agents call bazel_ios_get_bundle_id to retrieve information from XcodeBazelMCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool performs a retrieval operation on an already-built iOS app bundle to extract bundle identifier metadata. It has no side effects, does not execute code, does not modify data, and does not delete anything. The operation is purely informational and read-only, consistent with the Read category (search, list, get, fetch).
From the tool's definition Tool name contains 'get' and description states 'Extract CFBundleIdentifier from a built .app bundle' — a read-only query operation that retrieves metadata from an existing build artifact without modification or execution.
Documented attack patterns abuse exactly the kind of access bazel_ios_get_bundle_id gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and XcodeBazelMCP, and nothing reaches the server without passing your rules. This is the rule we recommend for bazel_ios_get_bundle_id:
{
"version": "1",
"default": "deny",
"tools": {
"bazel_ios_get_bundle_id": {}
}
} bazel_ios_get_bundle_id is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Extract CFBundleIdentifier from a built .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_ios_get_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_ios_get_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_ios_get_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_ios_get_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_ios_get_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.
Start from XcodeBazelMCP, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
117 XcodeBazelMCP tools catalogued and risk-classified — across an index of 43,000+ MCP servers.