transfer_collection_items · Postman MCP: Risk & Policy

WHAT IT DOES

What transfer_collection_items does on Postman

AI agents use transfer_collection_items 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 transfer_collection_items needs a policy

This tool moves items from one collection to another. It is a Write operation as it modifies the state of two collections (removing from source, adding to destination), but is likely reversible by transferring back. No destructive, financial, or execution semantics are indicated.

From the tool's definition Transfer items between collections

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

transfer_collection_items Rate-limited

transfer_collection_items 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": {
    "transfer_collection_items": {
      "limits": [
        {
          "counter": "transfer_collection_items_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 transfer_collection_items

What does the transfer_collection_items tool do? +

Transfer items between collections. 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 transfer_collection_items? +

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

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

Can I rate-limit transfer_collection_items? +

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

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

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

// THE FULL RECORD

transfer_collection_items is one line of Postman'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 →