update_collection_folder · Postman MCP: Risk & Policy

WHAT IT DOES

What update_collection_folder does on Postman

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

This tool modifies collection folder metadata or properties without deleting or destroying data. It uses PATCH semantics, meaning it only updates provided fields while preserving other data, making the change reversible through subsequent updates. This places it squarely in the Write category (modifies data reversibly) rather than Destructive, Execute, or Read.

From the tool's definition Tool name 'update_collection_folder' and description 'Update a folder in a collection. Acts like PATCH, only updates provided values' indicate modification of existing data in a reversible manner.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

update_collection_folder Rate-limited

update_collection_folder 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": {
    "update_collection_folder": {
      "limits": [
        {
          "counter": "update_collection_folder_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 update_collection_folder

What does the update_collection_folder tool do? +

Update a folder in a collection. Acts like PATCH, only updates provided values. 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 update_collection_folder? +

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

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

Can I rate-limit update_collection_folder? +

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

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

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