New Your team’s decisions, in one playbook every coding agent works from. Never answer your agent twice

bazel_ios_device_install_app

Install a previously built .app bundle onto a connected physical iOS device.

SERVERXcodeBazelMCP SOURCExcodebazelmcp/xcodebazelmcp
High RISK CLASS
Category Execute
Parameters 00 required
Recommended Rate-limitedsee the rule below
Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/xcodebazelmcp-xcodebazelmcp/bazel-ios-device-install-app.md

What bazel_ios_device_install_app does on XcodeBazelMCP

AI agents invoke bazel_ios_device_install_app to trigger actions in XcodeBazelMCP. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call: builds kicked off, notifications sent, workflows started.

Why bazel_ios_device_install_app is rated High

Installing an app onto a physical device triggers an external operation that modifies the device's state (adds/replaces an app). It is not purely destructive (doesn't delete data irreversibly), not financial, but executes an external operation with side effects on a connected device. Misuse could install malicious or unauthorized software on a physical device.

From the tool's definition Install a previously built .app bundle onto a connected physical iOS device

Questions about bazel_ios_device_install_app

What does the bazel_ios_device_install_app tool do? +

Install a previously built .app bundle onto a connected physical iOS device. It is categorised as a Execute tool in the XcodeBazelMCP MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on bazel_ios_device_install_app? +

Register the XcodeBazel MCP server in PolicyLayer and add a rule for bazel_ios_device_install_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.

What risk level is bazel_ios_device_install_app? +

bazel_ios_device_install_app is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit bazel_ios_device_install_app? +

Yes. Add a rate_limit block to the bazel_ios_device_install_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.

How do I block bazel_ios_device_install_app completely? +

Set action: deny in the PolicyLayer policy for bazel_ios_device_install_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.

What MCP server provides bazel_ios_device_install_app? +

bazel_ios_device_install_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.

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of XcodeBazel's. Pull the full record:

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.