AI agents invoke swift_package_build 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.
This tool invokes a Swift package build, which runs code compilation and linking operations. Build execution is a form of code execution with side effects on the file system (creating artifacts, intermediate files, etc.). While not immediately destructive, it can consume resources and potentially fail in ways that affect the build environment.
From the tool's definition Tool name 'swift_package_build' indicates execution of build operations. Description states 'Build a Swift package using' which confirms it triggers a build process (compilation and linking of code).
Documented attack patterns abuse exactly the kind of access swift_package_build gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and XcodeBazelMCP, and nothing reaches the server without passing your rules. This is the rule we recommend for swift_package_build:
{
"version": "1",
"default": "deny",
"tools": {
"swift_package_build": {
"limits": [
{
"counter": "swift_package_build_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
}swift_package_build 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.
Free to start. No card required.
Build 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.
Register the XcodeBazel MCP server in PolicyLayer and add a rule for swift_package_build: 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.
swift_package_build is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the swift_package_build 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.
Set action: deny in the PolicyLayer policy for swift_package_build. 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.
swift_package_build 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.
Start from XcodeBazelMCP, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
117 XcodeBazelMCP tools catalogued and risk-classified — across an index of 43,000+ MCP servers.