patch_collection
Partially update a collection. Only updates provided fields.
This record as markdown: /tools/delano-postman-mcp-server/patch-collection.md
What patch_collection does on Postman
AI agents use patch_collection 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 patch_collection is rated Medium
The tool modifies collection data via a PATCH operation, which is a Write action (reversible update). It does not create new collections (that's handled by create_collection), does not delete (Destructive), and does not execute arbitrary code (Execute). The severity is medium because unintended collection modifications could disrupt Postman workflows, but the change can typically be reverted.
From the tool's definition Tool name 'patch_collection' and description 'Partially update a collection. Only updates provided fields.' indicate reversible modification of collection metadata or structure.
Attacks that exploit this kind of access
The rule that runs patch_collection 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 patch_collection, this is the rule to start with:
patch_collection 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 patch_collection call is checked against it from then on.
Questions about patch_collection
Partially update a collection. Only updates provided fields. 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 patch_collection: 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.
patch_collection 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 patch_collection 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 patch_collection. 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.
patch_collection 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