AI agents call xcodebuild_show_destinations to retrieve information from Xctools without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool performs a read-only operation that queries and returns available build destinations (devices, simulators, etc.) for an Xcode project. It has no side effects, does not execute code, and does not modify any data. The blast radius of misuse is minimal—an attacker could only discover valid deployment targets, which does not compromise system security or project integrity.
From the tool's definition Tool name includes 'show' and description states it 'List valid destinations' — these are query operations that retrieve information without modification or execution of build/test operations.
Attacks that exploit this kind of access
List valid destinations for a project or workspace and scheme. It is categorised as a Read tool in the Xctools MCP Server, which means it retrieves data without modifying state.
Register the Xctools MCP server in PolicyLayer and add a rule for xcodebuild_show_destinations: 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 Xctools. Nothing to install.
xcodebuild_show_destinations 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 xcodebuild_show_destinations 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 xcodebuild_show_destinations. 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.
xcodebuild_show_destinations is provided by the Xctools MCP server (nzrsky/xctools-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →