package-resolve · Python MCP: Risk & Policy

WHAT IT DOES

What package-resolve does on Python

AI agents invoke package-resolve to trigger actions in Python. 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 IT NEEDS A POLICY

Why package-resolve needs a policy

Resolving package dependencies involves executing an external process (Swift Package Manager) that reaches out to external registries and may update Package.resolved files. This is more than a read — it executes an operation with side effects on the dependency graph — but is not purely destructive or financial. Execute is the most appropriate category given the active external operation and potential state changes.

From the tool's definition "Resolves Swift package dependencies" — this triggers an external package resolution operation (e.g., swift package resolve), which runs an external tool/process and may fetch/modify dependency lock files.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

package-resolve Rate-limited

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

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "package-resolve": {
      "limits": [
        {
          "counter": "package-resolve_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-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-resolve

What does the package-resolve tool do? +

Resolves Swift package dependencies and returns structured resolution results. It is categorised as a Execute tool in the Python MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

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

Register the Python MCP server in PolicyLayer and add a rule for package-resolve: 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-resolve? +

package-resolve is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit package-resolve? +

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

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

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