package-update

Updates Swift package dependencies and returns structured update results.

SERVERBuild SOURCEDave-London/Pare

Medium RISK CLASS

Category Write

Parameters 00 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/io-github-dave-london-build/package-update.md

WHAT IT DOES

What package-update does on Build

AI agents use package-update to create or update resources in Build, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Build environment.

RISK

Why package-update is rated Medium

This tool creates or modifies project dependencies reversibly by updating package versions. While updates can be undone by reverting the manifest or re-running with different versions, the tool itself performs write-level mutations to project configuration. It does not execute arbitrary code, delete data, or move funds.

From the tool's definition Tool name 'package-update' and description states it 'Updates Swift package dependencies' — a modification operation that changes package versions in a project's dependency manifest.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs package-update safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Build, 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 Rate-limited

package-update 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.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "package-update": {
      "limits": [
        {
          "counter": "package-update_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Build, apply this rule, and every package-update call is checked against it from then on.

FAQ

Questions about package-update

What does the package-update tool do? +

Updates Swift package dependencies and returns structured update results. It is categorised as a Write tool in the Build MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on package-update? +

Register the Build 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 Build. Nothing to install.

What risk level is package-update? +

package-update is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit package-update? +

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.

How do I block package-update completely? +

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.

What MCP server provides package-update? +

package-update is provided by the Build MCP server (Dave-London/Pare). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Build, and thousands of servers like it.

This server

All 202 Build tools →

Across the catalogue

create_package_backup on Android Forensics ADB MCP Server →aroflo_create_or_update_record on AroFlo MCP →team_manager_update_budget on Team Manager MCP → The MCP Attack Database →

Guides

Govern customer-ops agents →Argument validation →Scoped token →