Update collection metadata (name, description, variables)
AI agents use update_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.
This tool creates or modifies data in a reversible manner. Updating metadata like name, description, and variables are Write operations—the changes can be undone by updating again with previous values. It is not Destructive because no data is deleted or permanently lost, not Execute because it doesn't run external code or commands, and not Financial.
From the tool's definition The tool description explicitly states it updates collection metadata (name, description, variables), which modifies existing data reversibly without destroying it.
Documented attack patterns abuse exactly the kind of access update_collection gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Postman, and nothing reaches the server without passing your rules. This is the rule we recommend for update_collection:
{
"version": "1",
"default": "deny",
"tools": {
"update_collection": {
"limits": [
{
"counter": "update_collection_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}update_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.
Free to start. No card required.
Update collection metadata (name, description, variables). 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: 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 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 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. 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 is provided by the Postman MCP server (salehkhatri/postman-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 19 Postman tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
19 Postman tools catalogued and risk-classified — across an index of 42,500+ MCP servers.