vault_delete
Delete a vault entry by name. Requires your secret (Bearer).
This record as markdown: /tools/com-wingmanprotocol-agent-gateway/vault-delete.md
What vault_delete does on Gateway
AI agents call vault_delete to permanently remove resources in Gateway, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
| Parameter | Type | Required | Description |
|---|---|---|---|
name | string | Yes | the entry name to delete |
handle | string | Yes | your registered handle |
Parameters from the server's own tool schema.
Why vault_delete is rated Critical
Vault systems typically store sensitive credentials, keys, or important data. Deletion of vault entries cannot be undone and represents permanent loss of data. This satisfies the Destructive category definition: 'irreversibly deletes or overwrites data, or actions that cannot be undone (delete, drop, purge, force-push).' While authentication is required, a compromised or misdirected agent could still cause…
From the tool's definition Tool is named 'vault_delete' and description states 'Delete a vault entry by name' — this is an irreversible deletion operation. The mention of 'requires your secret (Bearer)' indicates it operates on sensitive stored data.
Attacks that exploit this kind of access
The rule that runs vault_delete safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Gateway, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For vault_delete, this is the rule to start with:
vault_delete 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 Gateway, apply this rule, and every vault_delete call is checked against it from then on.
Questions about vault_delete
Delete a vault entry by name. Requires your secret (Bearer). It is categorised as a Destructive tool in the Gateway MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
vault_delete accepts 2 parameters: name, handle. Required: name, handle. The full parameter table on this page comes from the server's own tool schema.
Register the Gateway MCP server in PolicyLayer and add a rule for vault_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 Gateway. Nothing to install.
vault_delete 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 vault_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.
Set action: deny in the PolicyLayer policy for vault_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.
vault_delete is provided by the Gateway MCP server (https://wingmanprotocol.com/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Gateway, and thousands of servers like it.
Across the catalogue