Soft-delete the latest version of a secret at secret/data/{path} (KV v2).
AI agents call delete_secret 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.
This tool deletes secret data, which is an irreversible operation. Even though described as 'soft-delete' (suggesting version history may be retained in Vault), the primary function is to remove access to secret data. In a security secrets management context, deletion of secrets constitutes a destructive action that cannot be undone by the tool itself.
From the tool's definition Tool name is 'delete_secret' and description states it performs a 'Soft-delete the latest version of a secret'. The action irreversibly removes secret data, even if soft-deleted rather than hard-deleted.
Documented attack patterns abuse exactly the kind of access delete_secret gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and HashiCorp Vault MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for delete_secret:
{
"version": "1",
"default": "deny",
"hide": [
"delete_secret"
]
}delete_secret disappears from the agent's tool list entirely, and any attempt to call it is denied. The rest of the server keeps working.
Free to start. No card required.
Soft-delete the latest version of a secret at secret/data/{path} (KV v2). 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.
Register the HashiCorp Vault MCP Server MCP server in PolicyLayer and add a rule for delete_secret: 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.
delete_secret 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_secret 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_secret. 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_secret is provided by the HashiCorp Vault MCP Server MCP server (rccyx/vault-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from HashiCorp Vault MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
4 HashiCorp Vault MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.