AI agents call xcode_get_build_settings to retrieve information from Xcode without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries and retrieves build settings information from an Xcode project without modifying, executing, or deleting anything. It is purely informational in nature, similar to a 'get' or 'fetch' operation. The blast radius if misused is minimal—an AI agent gaining this capability can only view build configuration data, not alter it or trigger builds.
From the tool's definition The tool description explicitly states it retrieves 'resolved build settings for a target and configuration.' The verb 'Get' and the action of retrieving/querying build configuration data indicates this is a read-only operation with no side effects.
Attacks that exploit this kind of access
Get resolved build settings for a target and configuration. It is categorised as a Read tool in the Xcode MCP Server, which means it retrieves data without modifying state.
Register the Xcode MCP server in PolicyLayer and add a rule for xcode_get_build_settings: 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 Xcode. Nothing to install.
xcode_get_build_settings 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 xcode_get_build_settings 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 xcode_get_build_settings. 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.
xcode_get_build_settings is provided by the Xcode MCP server (raunaksplanet/xcode-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 →