Updates the dependencies of your Swift project using Swift Package Manager.
AI agents use update_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 modifies project state by updating Swift package dependencies, which is a reversible write operation. While dependency updates can have significant side effects (pulling in new code, introducing vulnerabilities), the operation itself is not destructive (can be reverted) and does not execute arbitrary code or move money.
From the tool's definition Tool description states it 'Updates the dependencies of your Swift project using Swift Package Manager.' The word 'Updates' indicates modification of project configuration files (Package.swift, Package.resolved).
Documented attack patterns abuse exactly the kind of access update_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 update_swift_package:
{
"version": "1",
"default": "deny",
"tools": {
"update_swift_package": {
"limits": [
{
"counter": "update_swift_package_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}update_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.
Updates the dependencies of your Swift project using Swift Package Manager. 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 update_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.
update_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 update_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 update_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.
update_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.