Soft-delete a note by moving it to archives/.
AI agents call delete_note_tool to permanently remove resources in Alaya — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Although the deletion is 'soft' (moved to archives rather than permanently purged), it irreversibly removes the note from the user's active knowledge vault and standard retrieval paths. This is a destructive action that cannot be easily undone by an autonomous agent without explicit user intervention or access to archive operations.
From the tool's definition Tool name: delete_note_tool. Description states 'Soft-delete a note by moving it to archives/'. The operation removes a note from active access, preventing retrieval through normal workflows.
Attacks that exploit this kind of access
Soft-delete a note by moving it to archives/. It is categorised as a Destructive tool in the Alaya MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Alaya MCP server in PolicyLayer and add a rule for delete_note_tool: 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 Alaya. Nothing to install.
delete_note_tool 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_tool 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_tool. 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_tool is provided by the Alaya MCP server (luke-kucing/alaya). 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 →