delete_collection_access_key

Delete a collection access key

Server Postman postmanv3/postman-mcp-server
Category Destructive
Risk class Critical
Parameters 00 required

What delete_collection_access_key does on Postman

AI agents call delete_collection_access_key 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_access_key needs a policy

Deleting an access key is an irreversible action that permanently revokes authentication credentials. While not data deletion in the traditional sense, access keys are critical security artifacts whose removal cannot be undone—a new key must be generated. This fits the Destructive category as it removes a resource that cannot be restored.

From the tool's definition Tool name explicitly contains 'delete' and description states 'Delete a collection access key'. This operation removes authentication credentials that cannot be recovered without creating a new key.

Questions about delete_collection_access_key

What does the delete_collection_access_key tool do? +

Delete a collection access key. 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.

How do I enforce a policy on delete_collection_access_key? +

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

delete_collection_access_key is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.

Can I rate-limit delete_collection_access_key? +

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

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

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

// THE FULL RECORD

delete_collection_access_key is one line of Postman's registry record.

The record carries the whole server: verified identity, auth posture, risk grade, every tool classified, recommended policy — re-checked continuously.

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.