Delete a Vault key, secret, token, or folder.
AI agents call delete_vault_item to permanently remove resources in Pangea MCP Server — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
This tool permanently removes vault items (keys, secrets, tokens, folders) without reversal capability. Vault items are typically critical authentication credentials or sensitive data. Unauthorized deletion could break application authentication, cause data loss, or disable security controls. This meets the Destructive category as it irreversibly removes data that cannot be recovered.
From the tool's definition Tool name includes 'delete' and description states 'Delete a Vault key, secret, token, or folder' — irreversible removal of sensitive stored credentials and secrets.
Attacks that exploit this kind of access
Delete a Vault key, secret, token, or folder. It is categorised as a Destructive tool in the Pangea MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Pangea MCP Server MCP server in PolicyLayer and add a rule for delete_vault_item: 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 Pangea MCP Server. Nothing to install.
delete_vault_item 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_vault_item 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_vault_item. 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_vault_item is provided by the Pangea MCP Server MCP server (pangeacyber/pangea-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →