AI agents use create_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 new data (a Postman collection) within the Postman API, which is a Write operation. It is reversible since collections can be deleted, distinguishing it from Destructive. The severity is medium because creating unauthorized collections could clutter workspaces or be used to exfiltrate API requests/configurations, but the impact is limited to the Postman workspace and is remediable.
From the tool's definition Tool name 'create_collection' and description 'Create a new collection' indicate data creation. The tool adds a new collection to Postman workspaces, which is reversible via deletion.
Documented attack patterns abuse exactly the kind of access create_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 create_collection:
{
"version": "1",
"default": "deny",
"tools": {
"create_collection": {
"limits": [
{
"counter": "create_collection_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}create_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.
Create a new collection. 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 create_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.
create_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 create_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 create_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.
create_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.