Delete a note permanently. ONLY use this tool when the user explicitly requests note deletion (e.g.,
AI agents call delete_note to permanently remove resources in TriliumNext Notes' MCP Server — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
This tool permanently removes notes without reversibility, which is the defining characteristic of the Destructive category. Although the description is incomplete, the explicit mention of 'Delete a note permanently' provides strong evidence. The severity is high rather than critical because the blast radius is limited to individual notes within a note-taking application, not system-wide or financial impacts.
From the tool's definition Tool name 'delete_note' combined with description 'Delete a note permanently' explicitly indicates irreversible deletion of data.
Documented attack patterns abuse exactly the kind of access delete_note gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and TriliumNext Notes' MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for delete_note:
{
"version": "1",
"default": "deny",
"hide": [
"delete_note"
]
} delete_note disappears from the agent's tool list entirely, and any attempt to call it is denied. The rest of the server keeps working.
Free to start. No card required.
Delete a note permanently. ONLY use this tool when the user explicitly requests note deletion (e.g.,. It is categorised as a Destructive tool in the TriliumNext Notes' MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the TriliumNext Notes' 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 TriliumNext Notes' 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 TriliumNext Notes' MCP Server MCP server (tan-yong-sheng/triliumnext-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 11 TriliumNext Notes' MCP Server tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
11 TriliumNext Notes' MCP Server tools catalogued and risk-classified — across an index of 42,500+ MCP servers.