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

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

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

Questions about bazel_xcode_open_device_hub

What does the bazel_xcode_open_device_hub tool do? +

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.

How do I enforce a policy on bazel_xcode_open_device_hub? +

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.

What risk level is bazel_xcode_open_device_hub? +

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

Can I rate-limit bazel_xcode_open_device_hub? +

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.

How do I block bazel_xcode_open_device_hub completely? +

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.

What MCP server provides bazel_xcode_open_device_hub? +

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.

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