List connected physical iOS devices via devicectl.
AI agents call bazel_ios_list_devices to retrieve information from XcodeBazelMCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and enumerates connected iOS devices. It performs no side effects, creates no resources, executes no code, and modifies no state. It is a straightforward Read operation with minimal blast radius if misused by an agent — worst case, an attacker learns what devices are connected, which is low-impact information disclosure.
From the tool's definition Tool name includes 'list' and description states 'List connected physical iOS devices via devicectl' — a pure query operation with no modification, deletion, or execution of arbitrary commands.
Documented attack patterns abuse exactly the kind of access bazel_ios_list_devices gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and XcodeBazelMCP, and nothing reaches the server without passing your rules. This is the rule we recommend for bazel_ios_list_devices:
{
"version": "1",
"default": "deny",
"tools": {
"bazel_ios_list_devices": {}
}
}bazel_ios_list_devices is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
List connected physical iOS devices via devicectl. It is categorised as a Read tool in the XcodeBazelMCP MCP Server, which means it retrieves data without modifying state.
Register the XcodeBazel MCP server in PolicyLayer and add a rule for bazel_ios_list_devices: 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_list_devices is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the bazel_ios_list_devices 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_list_devices. 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_list_devices 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.
Start from XcodeBazelMCP, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
117 XcodeBazelMCP tools catalogued and risk-classified — across an index of 43,000+ MCP servers.