Initializes a new Swift Package Manager project in the current directory. Use this tool first if your project doesn
AI agents use init_swift_package to create or update resources in Xcode — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Xcode environment.
This tool creates new files and directories as part of Swift package initialization, which is reversible (files and directories can be deleted). This is a Write operation—it modifies the filesystem by adding new artifacts, but the changes are not irreversible like deletion would be.
From the tool's definition Tool name 'init_swift_package' combined with description 'Initializes a new Swift Package Manager project in the current directory' indicates creation of new project files and directory structures.
Documented attack patterns abuse exactly the kind of access init_swift_package gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Xcode, and nothing reaches the server without passing your rules. This is the rule we recommend for init_swift_package:
{
"version": "1",
"default": "deny",
"tools": {
"init_swift_package": {
"limits": [
{
"counter": "init_swift_package_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}init_swift_package 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.
Initializes a new Swift Package Manager project in the current directory. Use this tool first if your project doesn. It is categorised as a Write tool in the Xcode MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Xcode MCP server in PolicyLayer and add a rule for init_swift_package: 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 Xcode. Nothing to install.
init_swift_package 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 init_swift_package 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 init_swift_package. 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.
init_swift_package is provided by the Xcode MCP server (xcode-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 69 Xcode tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
69 Xcode tools catalogued and risk-classified — across an index of 42,500+ MCP servers.