update

Updates dependencies in the lock file. Optionally updates a single package.

SERVERCargo 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-cargo/update.md

WHAT IT DOES

What update does on Cargo

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

RISK

Why update is rated Medium

This tool modifies dependency versions in the lock file (a write operation), but the changes are reversible via version control, dependency rollback, or re-running the update command. It does not delete data irreversibly or execute arbitrary code during the update process itself, so it is Write rather than Destructive or Execute.

From the tool's definition 'Updates dependencies in the lock file' — modifies the Cargo.lock file, which is data that can be read and reverted through version control or re-running cargo commands.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs update safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Cargo, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For update, this is the rule to start with:

update Rate-limited

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": {
    "update": {
      "limits": [
        {
          "counter": "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 Cargo, apply this rule, and every update call is checked against it from then on.

FAQ

Questions about update

What does the update tool do? +

Updates dependencies in the lock file. Optionally updates a single package. It is categorised as a Write tool in the Cargo MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on update? +

Register the Cargo MCP server in PolicyLayer and add a rule for 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 Cargo. Nothing to install.

What risk level is update? +

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

Can I rate-limit update? +

Yes. Add a rate_limit block to the 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 update completely? +

Set action: deny in the PolicyLayer policy for 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 update? +

update is provided by the Cargo 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 Cargo, and thousands of servers like it.

This server

All 202 Cargo tools →

Across the catalogue

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 →