swift_package_run

Build and run an executable target in a Swift package using

SERVERXcodeBazelMCP SOURCExcodebazelmcp/xcodebazelmcp

High RISK CLASS

Category Execute

Parameters 00 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/xcodebazelmcp-xcodebazelmcp/swift-package-run.md

WHAT IT DOES

What swift_package_run does on XcodeBazelMCP

AI agents invoke swift_package_run to trigger actions in XcodeBazelMCP. 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.

RISK

Why swift_package_run is rated High

This tool directly executes code by building and running Swift package targets. While the description is incomplete, the core semantics of 'run' combined with 'executable target' clearly indicate code execution. An AI agent misusing this could execute arbitrary Swift code with the permissions of the build system, making it Execute rather than Write.

From the tool's definition Tool description explicitly states 'Build and run an executable target' which indicates execution of code.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs swift_package_run safely

PolicyLayer is an MCP gateway: it sits between your AI agents and XcodeBazelMCP, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For swift_package_run, this is the rule to start with:

swift_package_run Rate-limited

swift_package_run 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": {
    "swift_package_run": {
      "limits": [
        {
          "counter": "swift_package_run_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect XcodeBazelMCP, apply this rule, and every swift_package_run call is checked against it from then on.

FAQ

Questions about swift_package_run

What does the swift_package_run tool do? +

Build and run an executable target in a Swift package using. It is categorised as a Execute tool in the XcodeBazelMCP MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on swift_package_run? +

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

What risk level is swift_package_run? +

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

Can I rate-limit swift_package_run? +

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

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

swift_package_run is provided by the XcodeBazel MCP server (xcodebazelmcp/xcodebazelmcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on XcodeBazel, and thousands of servers like it.

This server

All 125 XcodeBazel tools → High-risk tools on this server →

Across the catalogue

run on 0sec →shortcuts_run on Apple Apps MCP →run_emba_scan on EMBA-MCP → All high-risk MCP tools → The MCP Attack Database →

Guides

Govern code and CI agents →Agent sandbox →Least privilege for MCP →