bazel_xcode_open_device_hub
Open DeviceHub.app — the GUI device manager bundled with Xcode-beta / Xcode 27 — to inspect, pair, and interact with physical devices. Falls back with guidance when no DeviceHub is installed (older Xcode).
This record as markdown: /tools/xcodebazelmcp-xcodebazelmcp/bazel-xcode-open-device-hub.md
What bazel_xcode_open_device_hub does on XcodeBazelMCP
AI agents invoke bazel_xcode_open_device_hub 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_xcode_open_device_hub is rated High
This tool launches an external application (DeviceHub.app) and triggers device pairing/interaction operations. Opening a GUI app and interacting with physical hardware goes beyond a simple read — it executes an external process with potential side effects on device state. Severity is medium since it operates on physical devices but is limited to a device management GUI context.
From the tool's definition Open DeviceHub.app — the GUI device manager bundled with Xcode-beta / Xcode 27 — to inspect, pair, and interact with physical devices
Attacks that exploit this kind of access
The rule that runs bazel_xcode_open_device_hub 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_xcode_open_device_hub, this is the rule to start with:
bazel_xcode_open_device_hub stays usable, but rate-capped: a runaway agent can't fire it dozens of times a minute. 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_xcode_open_device_hub call is checked against it from then on.
Questions about bazel_xcode_open_device_hub
Open DeviceHub.app — the GUI device manager bundled with Xcode-beta / Xcode 27 — to inspect, pair, and interact with physical devices. Falls back with guidance when no DeviceHub is installed (older Xcode). 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.
Register the XcodeBazel MCP server in PolicyLayer and add a rule for bazel_xcode_open_device_hub: 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_xcode_open_device_hub is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the bazel_xcode_open_device_hub 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_xcode_open_device_hub. 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_xcode_open_device_hub 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