Directly edit the Package.swift file of the active SPM project. This is useful for making changes that aren
AI agents use edit_package_swift 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.
The tool modifies Package.swift, a critical configuration file in Swift Package Manager projects. Edits are reversible (Write rather than Destructive), but misconfiguration can break builds, introduce dependencies, alter versioning, or compromise project integrity. High severity due to impact scope and blast radius of malformed package manifests.
From the tool's definition Directly edit the Package.swift file of the active SPM project.
Documented attack patterns abuse exactly the kind of access edit_package_swift 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 edit_package_swift:
{
"version": "1",
"default": "deny",
"tools": {
"edit_package_swift": {
"limits": [
{
"counter": "edit_package_swift_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}edit_package_swift 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.
Directly edit the Package.swift file of the active SPM project. This is useful for making changes that aren. 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 edit_package_swift: 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.
edit_package_swift 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 edit_package_swift 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 edit_package_swift. 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.
edit_package_swift 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.