bazel_ios_device_uninstall_app
Uninstall an app from a connected physical iOS device by bundle identifier.
This record as markdown: /tools/xcodebazelmcp-xcodebazelmcp/bazel-ios-device-uninstall-app.md
What bazel_ios_device_uninstall_app does on XcodeBazelMCP
AI agents call bazel_ios_device_uninstall_app to permanently remove resources in XcodeBazelMCP, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Why bazel_ios_device_uninstall_app is rated Critical
This tool performs an irreversible destructive action—removing an installed application from a physical iOS device. While not as severe as deleting user data directly, uninstalling an app cannot be undone through the tool itself and represents a destructive modification to the device state.
From the tool's definition The tool name explicitly contains 'uninstall_app' and the description states it will 'Uninstall an app from a connected physical iOS device.' Uninstalling an application is an irreversible action that removes software and associated data from the device.
Attacks that exploit this kind of access
The rule that runs bazel_ios_device_uninstall_app 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_device_uninstall_app, this is the rule to start with:
bazel_ios_device_uninstall_app is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.
The button opens the PolicyLayer dashboard: create your workspace, connect XcodeBazelMCP, apply this rule, and every bazel_ios_device_uninstall_app call is checked against it from then on.
Questions about bazel_ios_device_uninstall_app
Uninstall an app from a connected physical iOS device by bundle identifier. It is categorised as a Destructive tool in the XcodeBazelMCP MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the XcodeBazel MCP server in PolicyLayer and add a rule for bazel_ios_device_uninstall_app: 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_device_uninstall_app is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the bazel_ios_device_uninstall_app 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_device_uninstall_app. 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_device_uninstall_app 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