Removes a Swift Package dependency from the active project.
AI agents call remove_swift_package to permanently remove resources in Xcode — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Removing a package dependency is a destructive operation—it irreversibly deletes configuration state from the active Xcode project. While the package files themselves may still exist elsewhere, the dependency link is permanently severed until manually re-added. This is more severe than a Write operation because the action cannot be easily undone by an AI agent without additional steps.
From the tool's definition Tool name is 'remove_swift_package' and description states it 'Removes a Swift Package dependency from the active project.' The verb 'remove' in conjunction with 'dependency' indicates deletion of a project configuration that cannot be easily or automatically…
Documented attack patterns abuse exactly the kind of access remove_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 remove_swift_package:
{
"version": "1",
"default": "deny",
"hide": [
"remove_swift_package"
]
}remove_swift_package disappears from the agent's tool list entirely, and any attempt to call it is denied. The rest of the server keeps working.
Free to start. No card required.
Removes a Swift Package dependency from the active project. It is categorised as a Destructive tool in the Xcode MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Xcode MCP server in PolicyLayer and add a rule for remove_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.
remove_swift_package is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the remove_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 remove_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.
remove_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.