xcodebuild_test · Xctools MCP: Risk & Policy

WHAT IT DOES

What xcodebuild_test does on Xctools

AI agents invoke xcodebuild_test to trigger actions in Xctools. 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 xcodebuild_test needs a policy

The tool name strongly implies it runs xcodebuild's test action, which executes test suites against a project. This is an Execute-category action as it runs code/processes. The description is empty, reducing confidence slightly, but context from sibling tools (xcodebuild_build, xcodebuild_archive) and server description confirm it triggers external build/test operations.

From the tool's definition Tool name 'xcodebuild_test' on a server described as providing access to 'xcodebuild' for 'building, testing, and analyzing projects'

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

xcodebuild_test Rate-limited

xcodebuild_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": {
    "xcodebuild_test": {
      "limits": [
        {
          "counter": "xcodebuild_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 Xctools, so you can run agents against it safely.

FAQ

Questions about xcodebuild_test

What does the xcodebuild_test tool do? +

xcodebuild_test. It is categorised as a Execute tool in the Xctools MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on xcodebuild_test? +

Register the Xctools MCP server in PolicyLayer and add a rule for xcodebuild_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 Xctools. Nothing to install.

What risk level is xcodebuild_test? +

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

Can I rate-limit xcodebuild_test? +

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

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

xcodebuild_test is provided by the Xctools MCP server (nzrsky/xctools-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.