xcode_open_project · Xcode MCP: Risk & Policy

WHAT IT DOES

What xcode_open_project does on Xcode

AI agents invoke xcode_open_project 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.

WHY IT NEEDS A POLICY

Why xcode_open_project needs a policy

This tool uses osascript (Apple Script execution) to trigger an external application action (opening Xcode). It runs a script/command to interact with an external process, making it Execute category. The blast radius is medium — it launches Xcode with a specified project, which could expose project contents or trigger Xcode's automatic actions, but doesn't directly modify or delete data.

From the tool's definition Open .xcodeproj or .xcworkspace in Xcode via osascript

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

xcode_open_project Rate-limited

xcode_open_project stays usable, but rate-capped — a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "xcode_open_project": {
      "limits": [
        {
          "counter": "xcode_open_project_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Xcode, so you can run agents against it safely.

FAQ

Questions about xcode_open_project

What does the xcode_open_project tool do? +

Open .xcodeproj or .xcworkspace in Xcode via osascript. 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.

How do I enforce a policy on xcode_open_project? +

Register the Xcode MCP server in PolicyLayer and add a rule for xcode_open_project: 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.

What risk level is xcode_open_project? +

xcode_open_project is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit xcode_open_project? +

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

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

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