package-update
Updates Swift package dependencies and returns structured update results.
This record as markdown: /tools/io-github-dave-london-docker/package-update.md
What package-update does on Docker
AI agents invoke package-update to trigger actions in Docker. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call: builds kicked off, notifications sent, workflows started.
Why package-update is rated High
Updating package dependencies executes an external operation (swift package update) that fetches and installs new dependency versions, modifying the project's Package.resolved file and potentially pulling in new code. This is more than a simple write — it triggers external network operations and code execution pipelines.
From the tool's definition 'Updates Swift package dependencies' — triggers an external package resolution/download operation that modifies the dependency graph and potentially installs new code
Attacks that exploit this kind of access
The rule that runs package-update safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Docker, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For package-update, this is the rule to start with:
package-update stays usable, but rate-capped: a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Docker, apply this rule, and every package-update call is checked against it from then on.
Questions about package-update
Updates Swift package dependencies and returns structured update results. It is categorised as a Execute tool in the Docker MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Docker MCP server in PolicyLayer and add a rule for package-update: 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 Docker. Nothing to install.
package-update is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the package-update 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 package-update. 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.
package-update is provided by the Docker MCP server (@paretools/docker). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Docker, and thousands of servers like it.
Across the catalogue