bazel_ios_device_unpair

Unpair a previously paired physical iOS device.

SERVERXcodeBazelMCP SOURCExcodebazelmcp/xcodebazelmcp

Critical RISK CLASS

Category Destructive

Parameters 00 required

Recommended Hiddensee the rule below

Registry record Grade F, identity unverified Pull the record →

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

WHAT IT DOES

What bazel_ios_device_unpair does on XcodeBazelMCP

AI agents call bazel_ios_device_unpair 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.

RISK

Why bazel_ios_device_unpair is rated Critical

Unpairing a device is an irreversible action that removes the trust relationship between the host and the physical iOS device. Restoring this pairing requires manual intervention (physical device interaction and re-trust confirmation), making it non-trivially reversible. Misuse could disrupt development workflows by breaking device connectivity.

From the tool's definition Unpair a previously paired physical iOS device

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs bazel_ios_device_unpair 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_unpair, this is the rule to start with:

bazel_ios_device_unpair Hidden

bazel_ios_device_unpair is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "hide": [
    "bazel_ios_device_unpair"
  ]
}

RESTRICT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect XcodeBazelMCP, apply this rule, and every bazel_ios_device_unpair call is checked against it from then on.

FAQ

Questions about bazel_ios_device_unpair

What does the bazel_ios_device_unpair tool do? +

Unpair a previously paired physical iOS device. 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.

How do I enforce a policy on bazel_ios_device_unpair? +

Register the XcodeBazel MCP server in PolicyLayer and add a rule for bazel_ios_device_unpair: 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_unpair? +

bazel_ios_device_unpair is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.

Can I rate-limit bazel_ios_device_unpair? +

Yes. Add a rate_limit block to the bazel_ios_device_unpair 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_unpair completely? +

Set action: deny in the PolicyLayer policy for bazel_ios_device_unpair. 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_unpair? +

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

KEEP EXPLORING

More on XcodeBazel, and thousands of servers like it.

This server

All 125 XcodeBazel tools → Critical-risk tools on this server →

Across the catalogue

All critical-risk MCP tools → The MCP Attack Database →

Guides

Govern database agents →Blast radius →Tool call approval →