AI agents invoke xcode_get_analyzer_results to trigger actions in Xcode. 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.
This tool executes the Xcode static analyzer, which is an active process that runs against the codebase. While it only reads and reports issues without modifying files, it triggers an external build-system operation rather than passively querying existing data, placing it in the Execute category. Misuse risk is medium as it consumes build resources and could expose code issues but does not modify or delete anything.
From the tool's definition 'Run the static analyzer and return issues' — actively runs an analysis process
Attacks that exploit this kind of access
Run the static analyzer and return issues. It is categorised as a Execute tool in the Xcode MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Xcode MCP server in PolicyLayer and add a rule for xcode_get_analyzer_results: 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_analyzer_results is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the xcode_get_analyzer_results 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_analyzer_results. 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_analyzer_results 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 →