vault_delete
A destructive tool on the Looking Glass MCP server.
This record as markdown: /tools/io-github-sahib-sawhney-wh-looking-glass-mcp/vault-delete.md
What vault_delete does on Looking Glass
AI agents call vault_delete to permanently remove resources in Looking Glass, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
| Parameter | Type | Required | Description |
|---|---|---|---|
profile | string | Yes | Profile name to delete |
Parameters from the server's own tool schema.
Why vault_delete is rated Critical
The name explicitly contains 'delete', which maps to the Destructive category per the classification rules. A vault typically stores sensitive or important data; deleting vault contents is an irreversible operation. The empty description lowers confidence slightly, but the semantic meaning of 'delete' on a 'vault' is unambiguous.
From the tool's definition Tool name 'vault_delete' indicates deletion operation. In the context of a 'vault' (secure storage system), deletion is irreversible data destruction. While the description is empty, the name strongly suggests removal of stored data without undo capability.
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 Looking Glass, 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 Looking Glass, apply this rule, and every vault_delete call is checked against it from then on.
Questions about vault_delete
vault_delete is a destructive tool on the Looking Glass MCP server. It is categorised as a Destructive tool in the Looking Glass MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
vault_delete accepts 1 parameter: profile. Required: profile. The full parameter table on this page comes from the server's own tool schema.
Register the Looking Glass 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 Looking Glass. 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 Looking Glass MCP server (looking-glass-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Looking Glass, and thousands of servers like it.
Across the catalogue