Delete a note (moves to .trash folder)
AI agents call delete_note to permanently remove resources in Multi-Tool MCP Server — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
This tool irreversibly removes data (notes) from the active vault, matching the Destructive category definition. Although technically recoverable from a .trash folder, the operation cannot be undone through normal tool interaction and represents loss of data availability.
From the tool's definition Tool name is 'delete_note' and description states it 'Delete[s] a note'; while the note is moved to a trash folder rather than permanently purged, the deletion action is irreversible from the user's perspective and removes data from active access.
Attacks that exploit this kind of access
Delete a note (moves to .trash folder). It is categorised as a Destructive tool in the Multi-Tool MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Multi-Tool MCP Server 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 Multi-Tool MCP Server. 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 Multi-Tool MCP Server MCP server (shawn-falconbury/mcp-server). 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 →