pull_collection_changes
Pull changes from parent collection into forked collection
This record as markdown: /tools/delano-postman-mcp-server/pull-collection-changes.md
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 pull_collection_changes is rated Medium
This tool merges/pulls changes from a parent collection into a forked collection, modifying the forked collection's content. This is a reversible write operation (updating/syncing data) rather than destructive, since it doesn't delete data but does overwrite the fork's state with upstream changes. Misuse could unintentionally overwrite work in a forked collection.
From the tool's definition Pull changes from parent collection into forked collection
Attacks that exploit this kind of access
The rule that runs pull_collection_changes safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Postman, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For pull_collection_changes, this is the rule to start with:
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.
The button opens the PolicyLayer dashboard: create your workspace, connect Postman, apply this rule, and every pull_collection_changes call is checked against it from then on.
Questions about pull_collection_changes
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.
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.
pull_collection_changes is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
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.
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.
pull_collection_changes is provided by the Postman MCP server (delano/postman-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Postman, and thousands of servers like it.
This server
Across the catalogue