crow_trilium_delete_note
Delete a note from TriliumNext. Requires explicit confirmation.
This record as markdown: /tools/kh0pper-crow/crow-trilium-delete-note.md
What crow_trilium_delete_note does on Crow
AI agents call crow_trilium_delete_note to permanently remove resources in Crow, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Why crow_trilium_delete_note is rated Critical
This tool permanently removes data (a note) from the TriliumNext system. Even though it requires explicit confirmation, the underlying operation is destructive and cannot be undone. Destructive actions take precedence over Write category, as deletion cannot be reversed.
From the tool's definition Tool name contains 'delete' and description states 'Delete a note from TriliumNext.' The action is irreversible data removal.
Attacks that exploit this kind of access
The rule that runs crow_trilium_delete_note safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Crow, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For crow_trilium_delete_note, this is the rule to start with:
crow_trilium_delete_note 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 Crow, apply this rule, and every crow_trilium_delete_note call is checked against it from then on.
Questions about crow_trilium_delete_note
Delete a note from TriliumNext. Requires explicit confirmation. It is categorised as a Destructive tool in the Crow MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Crow MCP server in PolicyLayer and add a rule for crow_trilium_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 Crow. Nothing to install.
crow_trilium_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 crow_trilium_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 crow_trilium_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.
crow_trilium_delete_note is provided by the Crow MCP server (kh0pper/crow). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Crow, and thousands of servers like it.
Across the catalogue