Delete a note. Requires write_enabled=true AND expected_hash (no blind deletes).
AI agents call delete_note to permanently remove resources in Vault Memory — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Deletion of notes is irreversible data destruction. Even though the tool requires a hash parameter to prevent blind deletes, this is a safety guardrail rather than a category change—the tool's core function is to permanently remove data without possibility of recovery (unless separately backed up).
From the tool's definition Tool name is 'delete_note' with description stating 'Delete a note.' This is an irreversible deletion operation. The hash requirement mitigates accidental deletion but does not change the fundamental destructive nature of the action.
Attacks that exploit this kind of access
Delete a note. Requires write_enabled=true AND expected_hash (no blind deletes). It is categorised as a Destructive tool in the Vault Memory MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Vault Memory MCP server in PolicyLayer and add a rule for delete_note: 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 Memory. Nothing to install.
delete_note 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_note 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_note. 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_note is provided by the Vault Memory MCP server (owrede/vault-memory). 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 →