delete_virtual_key
Delete a virtual key by slug. This is irreversible and will break prompts and configs that reference the slug, so confirm no active dependencies first. Returns success after removal.
This record as markdown: /tools/codeswhat-portkey-admin-mcp/delete-virtual-key.md
What delete_virtual_key does on Portkey Admin
AI agents call delete_virtual_key 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_virtual_key is rated Critical
This tool performs an irreversible deletion that can have cascading negative effects on dependent prompts and configs. While not directly financial, the irreversible nature and potential to break active dependencies places it in the Destructive category with high severity—an AI agent misusing this could permanently delete critical infrastructure keys and cascade failures across the system.
From the tool's definition The description explicitly states 'Delete a virtual key by slug. This is irreversible' and warns that it 'will break prompts and configs that reference the slug'.
Attacks that exploit this kind of access
The rule that runs delete_virtual_key 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_virtual_key, this is the rule to start with:
delete_virtual_key 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_virtual_key call is checked against it from then on.
Questions about delete_virtual_key
Delete a virtual key by slug. This is irreversible and will break prompts and configs that reference the slug, so confirm no active dependencies first. Returns success after removal. 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_virtual_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 Portkey Admin. Nothing to install.
delete_virtual_key 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_virtual_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.
Set action: deny in the PolicyLayer policy for delete_virtual_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.
delete_virtual_key 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