merge_collection_fork

Merge a forked collection back into its parent

SERVERPostman SOURCEdelano/postman-mcp-server

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/delano-postman-mcp-server/merge-collection-fork.md

WHAT IT DOES

What merge_collection_fork does on Postman

AI agents use merge_collection_fork 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.

RISK

Why merge_collection_fork is rated Medium

Merging a fork modifies the parent collection's state by integrating new or changed elements, making it a reversible Write operation rather than Read (it changes data) or Destructive (merge can typically be undone or the parent's state reconstructed).

From the tool's definition Tool description states 'Merge a forked collection back into its parent', which modifies the parent collection by integrating changes from a fork.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs merge_collection_fork 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 merge_collection_fork, this is the rule to start with:

merge_collection_fork Rate-limited

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

FAQ

Questions about merge_collection_fork

What does the merge_collection_fork tool do? +

Merge a forked collection back into its parent. 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 merge_collection_fork? +

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

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

Can I rate-limit merge_collection_fork? +

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

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

merge_collection_fork 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.

KEEP EXPLORING

What merge_collection_fork does on Postman

Why merge_collection_fork is rated Medium

The rule that runs merge_collection_fork safely

Questions about merge_collection_fork

More on Postman, and thousands of servers like it.