This record as markdown: /tools/delano-postman-mcp-server/delete-collection.md
What delete_collection does on Postman
AI agents call delete_collection to permanently remove resources in Postman, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Why delete_collection is rated Critical
This tool permanently removes a collection and its contents, which cannot be undone. Deletion is irreversible and results in loss of data. While not financial in nature, the destructive impact—especially if an AI agent mistakenly deletes an important collection—justifies the Destructive category and high severity. Confidence is high because the intent is explicit in both name and description.
From the tool's definition Tool name is 'delete_collection' with description 'Delete a collection'. The verb 'delete' indicates irreversible removal of data.
Attacks that exploit this kind of access
The rule that runs delete_collection 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 delete_collection, this is the rule to start with:
delete_collection is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.
The button opens the PolicyLayer dashboard: create your workspace, connect Postman, apply this rule, and every delete_collection call is checked against it from then on.
Questions about delete_collection
Delete a collection. It is categorised as a Destructive tool in the Postman MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Postman MCP server in PolicyLayer and add a rule for delete_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.
delete_collection is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the delete_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 delete_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.
delete_collection 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.
Across the catalogue