bazel_ios_get_app_container
Get the on-disk container path for an installed app on a simulator (simctl get_app_container).
This record as markdown: /tools/xcodebazelmcp-xcodebazelmcp/bazel-ios-get-app-container.md
What bazel_ios_get_app_container does on XcodeBazelMCP
AI agents call bazel_ios_get_app_container 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_get_app_container is rated Low
This tool performs a read-only query operation on simulator state to retrieve the file system path where an app container is located. It has no side effects, does not execute code, does not modify state, and does not delete or move data. It is analogous to a filesystem lookup or metadata query.
From the tool's definition Tool description states "Get the on-disk container path for an installed app on a simulator". The verb "get" and the function "simctl get_app_container" indicate a retrieval operation that queries filesystem metadata without modifying or deleting data.
Attacks that exploit this kind of access
The rule that runs bazel_ios_get_app_container 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_get_app_container, this is the rule to start with:
bazel_ios_get_app_container 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_get_app_container call is checked against it from then on.
Questions about bazel_ios_get_app_container
Get the on-disk container path for an installed app on a simulator (simctl get_app_container). 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_app_container: 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_app_container 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_app_container 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_app_container. 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_app_container 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