xcode_test · Xclaude Plugin MCP: Risk & Policy

WHAT IT DOES

What xcode_test does on Xclaude Plugin

AI agents invoke xcode_test to trigger actions in Xclaude Plugin. 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_test needs a policy

This tool executes a test suite against an Xcode/iOS project. Running tests can trigger compilation, code execution, simulator interactions, and access to app containers. Misuse could cause unintended side effects such as consuming significant compute resources, triggering builds, or executing arbitrary test code. This clearly falls under Execute as it runs external operations.

From the tool's definition 'Run Xcode test suite for iOS apps' — explicitly runs/executes a test suite

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

xcode_test Rate-limited

xcode_test 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_test": {
      "limits": [
        {
          "counter": "xcode_test_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 Xclaude Plugin, so you can run agents against it safely.

FAQ

Questions about xcode_test

What does the xcode_test tool do? +

Run Xcode test suite for iOS apps. Check project. It is categorised as a Execute tool in the Xclaude Plugin 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_test? +

Register the Xclaude Plugin MCP server in PolicyLayer and add a rule for xcode_test: 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 Xclaude Plugin. Nothing to install.

What risk level is xcode_test? +

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

Can I rate-limit xcode_test? +

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

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

xcode_test is provided by the Xclaude Plugin MCP server (conorluddy/xclaude-plugin). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

// THE FULL RECORD

xcode_test is one line of Xclaude Plugin's registry record.

The record carries the whole server: verified identity, auth posture, risk grade, every tool classified, recommended policy — re-checked continuously.

Teams ship this data inside their own products. See what a licence covers →