update_collection_roles · Postman MCP: Risk & Policy

WHAT IT DOES

What update_collection_roles does on Postman

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

This tool modifies collection role assignments, which is a Write operation (reversible configuration change). It does not delete roles (Destructive), execute code (Execute), or move money (Financial). Severity is medium because role misconfiguration could grant unintended access to collections, but the operation is reversible and scoped to role metadata rather than collection data itself.

From the tool's definition Tool name 'update_collection_roles' and description 'Update collection roles' indicate modification of access control metadata. The parenthetical '(requires EDITOR role)' confirms this modifies permissions/roles rather than deleting them.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

update_collection_roles Rate-limited

update_collection_roles 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_roles": {
      "limits": [
        {
          "counter": "update_collection_roles_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_roles

What does the update_collection_roles tool do? +

Update collection roles (requires EDITOR role). 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_roles? +

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

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

Can I rate-limit update_collection_roles? +

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

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

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