Initialize a new Swift package in the given directory (
AI agents use swift_package_init to create or update resources in XcodeBazelMCP — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your XcodeBazelMCP environment.
This tool creates new files and directory structure for a Swift package. It's a Write operation as it creates new data (package files, configuration) in the filesystem. While it modifies the filesystem, it's reversible by deleting the created files. Severity is medium as misuse could overwrite or pollute a directory with unwanted package scaffolding.
From the tool's definition Initialize a new Swift package in the given directory
Documented attack patterns abuse exactly the kind of access swift_package_init 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_init:
{
"version": "1",
"default": "deny",
"tools": {
"swift_package_init": {
"limits": [
{
"counter": "swift_package_init_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}swift_package_init stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Initialize a new Swift package in the given directory (. It is categorised as a Write tool in the XcodeBazelMCP MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the XcodeBazel MCP server in PolicyLayer and add a rule for swift_package_init: 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_init is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the swift_package_init 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_init. 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_init 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.