vault_kv_delete

Delete the latest KV secret from HashiCorp Vault at the specified path

Server HashiCorp Vault MCP Server rod-anami-kyndryl/hashi-vault-mcp
Category Destructive
Risk class Critical
Parameters 00 required

What vault_kv_delete does on HashiCorp Vault MCP Server

AI agents call vault_kv_delete to permanently remove resources in HashiCorp Vault MCP Server — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.

Why vault_kv_delete needs a policy

This tool permanently removes secrets from Vault without possibility of reversal. Secrets in a secret management system are critical security assets—their deletion cannot be undone and could break authentication, encryption, or access to protected resources. An AI agent with misuse potential could delete production credentials, encryption keys, or API tokens, causing system-wide outages or security breaches.

From the tool's definition Tool name 'vault_kv_delete' and description 'Delete the latest KV secret from HashiCorp Vault at the specified path' explicitly perform irreversible deletion of secrets.

Questions about vault_kv_delete

What does the vault_kv_delete tool do? +

Delete the latest KV secret from HashiCorp Vault at the specified path. It is categorised as a Destructive tool in the HashiCorp Vault MCP Server 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 vault_kv_delete? +

Register the HashiCorp Vault MCP Server MCP server in PolicyLayer and add a rule for vault_kv_delete: 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 HashiCorp Vault MCP Server. Nothing to install.

What risk level is vault_kv_delete? +

vault_kv_delete 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 vault_kv_delete? +

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

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

vault_kv_delete is provided by the HashiCorp Vault MCP Server MCP server (rod-anami-kyndryl/hashi-vault-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

// LOOK UP ANOTHER 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 →

// GET IN TOUCH

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

Message sent.

We'll get back to you soon.