pull_collection_changes · Postman MCP: Risk & Policy

WHAT IT DOES

What pull_collection_changes does on Postman

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

WHY IT NEEDS A POLICY

Why pull_collection_changes needs a policy

This tool merges/synchronizes changes from a parent collection into a forked collection, modifying the forked collection's contents. This is a reversible write operation (the fork is updated with new data), not destructive since it doesn't delete anything permanently. Misuse could overwrite intentional customizations in the fork, hence medium severity.

From the tool's definition Pull changes from parent collection into forked collection

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

pull_collection_changes Rate-limited

pull_collection_changes 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": {
    "pull_collection_changes": {
      "limits": [
        {
          "counter": "pull_collection_changes_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 Postman, so you can run agents against it safely.

FAQ

Questions about pull_collection_changes

What does the pull_collection_changes tool do? +

Pull changes from parent collection into forked collection. It is categorised as a Write tool in the Postman MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on pull_collection_changes? +

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

What risk level is pull_collection_changes? +

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

Can I rate-limit pull_collection_changes? +

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

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

pull_collection_changes is provided by the Postman MCP server (postmanv3/postman-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.