update_collection_roles
Update collection roles (requires EDITOR role)
This record as markdown: /tools/delano-postman-mcp-server/update-collection-roles.md
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 update_collection_roles is rated Medium
The tool creates or modifies role permissions within a collection, which is a reversible change (roles can be updated again). It does not delete data irreversibly, execute arbitrary code, or move money. The blast radius is medium because misconfiguring collection roles could grant unintended access to sensitive API definitions and test data, but changes are auditable and correctable.
From the tool's definition Tool name includes 'update' and description states 'Update collection roles' — this modifies existing data (role assignments) reversibly within Postman collections.
Attacks that exploit this kind of access
The rule that runs update_collection_roles 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 update_collection_roles, this is the rule to start with:
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.
The button opens the PolicyLayer dashboard: create your workspace, connect Postman, apply this rule, and every update_collection_roles call is checked against it from then on.
Questions about update_collection_roles
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.
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.
update_collection_roles 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 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.
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.
update_collection_roles 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