update_collection_request · Postman MCP: Risk & Policy

WHAT IT DOES

What update_collection_request does on Postman

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

This tool modifies existing collection requests reversibly. It does not execute requests, delete them, or perform financial operations. The constraint 'Cannot change request folder' confirms it performs a bounded modification rather than destructive or execute operations. Update operations are classified as Write.

From the tool's definition Tool name is 'update_collection_request' and description states 'Update a request in a collection.' The word 'Update' indicates modification of existing data.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

update_collection_request Rate-limited

update_collection_request 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_request": {
      "limits": [
        {
          "counter": "update_collection_request_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_request

What does the update_collection_request tool do? +

Update a request in a collection. Cannot change request folder. 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_request? +

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

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

Can I rate-limit update_collection_request? +

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

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

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