kv2-destroy-versions
AI agents call kv2-destroy-versions to permanently remove resources in Vault MCP Server (mschuchard) — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
The tool name clearly indicates permanent deletion of KV v2 secret versions in HashiCorp Vault. This is an irreversible operation that destroys data and cannot be undone. While the description is empty, the name alone provides sufficient evidence. This falls into the Destructive category with high severity due to the potential loss of critical secrets and audit trail impact.
From the tool's definition Tool name 'kv2-destroy-versions' explicitly indicates destruction of secret engine data; 'destroy' combined with 'versions' in a Vault KV v2 context means irreversible deletion of secret versions.
Attacks that exploit this kind of access
kv2-destroy-versions. It is categorised as a Destructive tool in the Vault MCP Server (mschuchard) MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Vault MCP Server (mschuchard) MCP server in PolicyLayer and add a rule for kv2-destroy-versions: 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 Vault MCP Server (mschuchard). Nothing to install.
kv2-destroy-versions 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 kv2-destroy-versions 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 kv2-destroy-versions. 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.
kv2-destroy-versions is provided by the Vault MCP Server (mschuchard) MCP server (mschuchard/vault-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 →