High Risk →

test_swift_package

Tests a Swift Package using Swift Package Manager.

How to control test_swift_package ↓

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

High Risk

This tool executes tests via Swift Package Manager, which involves running code. It triggers external build and test processes whose effects depend on the package and test arguments. While not destructive or financial, it falls under Execute as it runs code/commands.

From the tool's definition 'Tests a Swift Package using Swift Package Manager' — runs test execution against a Swift package

Documented attack patterns abuse exactly the kind of access test_swift_package gives an agent:

PolicyLayer is an MCP gateway — it sits between your AI agents and Xcode, and nothing reaches the server without passing your rules. This is the rule we recommend for test_swift_package:

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "test_swift_package": {
      "limits": [
        {
          "counter": "test_swift_package_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

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

  1. Create a free account and register Xcode — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
RATE-LIMIT THIS TOOL →

Free to start. No card required.

Go deeper

What does the test_swift_package tool do? +

Tests a Swift Package using Swift Package Manager. 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 test_swift_package? +

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

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

Can I rate-limit test_swift_package? +

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

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

test_swift_package is provided by the Xcode MCP server (xcode-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Xcode tool call.

Deterministic rules across all 69 Xcode tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

Free to start. No card required.

69 Xcode tools catalogued and risk-classified — across an index of 42,500+ MCP servers.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.