transfer_collection_items
Transfer items between collections
This record as markdown: /tools/delano-postman-mcp-server/transfer-collection-items.md
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 transfer_collection_items is rated Medium
Transferring items between collections moves data from one location to another, which is a write/modify operation. It creates or modifies collection contents reversibly. The blast radius is medium as it could reorganize collection structure across multiple collections, but it doesn't permanently delete data.
From the tool's definition Transfer items between collections
Attacks that exploit this kind of access
The rule that runs transfer_collection_items 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 transfer_collection_items, this is the rule to start with:
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.
The button opens the PolicyLayer dashboard: create your workspace, connect Postman, apply this rule, and every transfer_collection_items call is checked against it from then on.
Questions about transfer_collection_items
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.
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.
transfer_collection_items 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 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.
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.
transfer_collection_items 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