package-update · Python MCP: Risk & Policy

WHAT IT DOES

What package-update does on Python

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

WHY IT NEEDS A POLICY

Why package-update needs a policy

The tool creates or modifies project dependencies reversibly (packages can be downgraded or pinned to different versions). While it affects a project's configuration, the changes are not permanent deletions and can be undone via version control or re-running with different parameters. This qualifies as Write rather than Destructive.

From the tool's definition Tool description states it 'Updates Swift package dependencies' — this is a modification operation that changes package versions/dependencies in a project.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

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.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Python, so you can run agents against it safely.

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 Python 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 Python 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 Python. 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 Python MCP server (Dave-London/Pare). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

// THE FULL RECORD

package-update is one line of Python's registry record.

The record carries the whole server: verified identity, auth posture, risk grade, every tool classified, recommended policy — re-checked continuously.

Teams ship this data inside their own products. See what a licence covers →