delete_collection
Delete a prompt collection by ID. This cannot be undone; prompts stay in the workspace but lose their collection grouping, so reassign them first if organization matters.
This record as markdown: /tools/codeswhat-portkey-admin-mcp/delete-collection.md
What delete_collection does on Portkey Admin
AI agents call delete_collection to permanently remove resources in Portkey Admin, 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
Although the deletion is non-total (prompts remain in the workspace), the collection itself is permanently removed and cannot be recovered. This irreversible data loss qualifies as destructive. The severity is high rather than critical because the impact is scoped to collection metadata rather than bulk data destruction, but the irreversible nature places it in the Destructive category rather than Write.
From the tool's definition Tool description explicitly states: 'Delete a prompt collection by ID. This cannot be undone' — the phrase 'cannot be undone' is the defining characteristic of destructive operations.
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 Portkey Admin, 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 Portkey Admin, apply this rule, and every delete_collection call is checked against it from then on.
Questions about delete_collection
Delete a prompt collection by ID. This cannot be undone; prompts stay in the workspace but lose their collection grouping, so reassign them first if organization matters. It is categorised as a Destructive tool in the Portkey Admin MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Portkey Admin 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 Portkey Admin. 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 Portkey Admin MCP server (codeswhat/portkey-admin-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Portkey Admin, and thousands of servers like it.
Across the catalogue