Browse the TriliumNext note tree from a starting note, showing children to a given depth.
AI agents call crow_trilium_browse_tree to retrieve information from Crow without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and displays note hierarchy information without creating, modifying, deleting, executing code, or moving money. It is a straightforward read operation on a note management system. Low severity because unauthorized access to note titles/structure poses minimal risk compared to other categories.
From the tool's definition Tool description states 'Browse the TriliumNext note tree from a starting note, showing children to a given depth' — uses 'browse' and 'showing', indicating read-only retrieval of hierarchical note data with no modification or execution.
Documented attack patterns abuse exactly the kind of access crow_trilium_browse_tree gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Crow, and nothing reaches the server without passing your rules. This is the rule we recommend for crow_trilium_browse_tree:
{
"version": "1",
"default": "deny",
"tools": {
"crow_trilium_browse_tree": {}
}
}crow_trilium_browse_tree is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Browse the TriliumNext note tree from a starting note, showing children to a given depth. It is categorised as a Read tool in the Crow MCP Server, which means it retrieves data without modifying state.
Register the Crow MCP server in PolicyLayer and add a rule for crow_trilium_browse_tree: 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_browse_tree is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the crow_trilium_browse_tree 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_browse_tree. 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_browse_tree 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.
Start from Crow, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
576 Crow tools catalogued and risk-classified — across an index of 43,000+ MCP servers.