This record as markdown: /tools/kh0pper-crow/crow-trilium-recent.md
What crow_trilium_recent does on Crow
AI agents call crow_trilium_recent to retrieve information from Crow without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why crow_trilium_recent is rated Low
This tool queries and retrieves recently modified notes from TriliumNext, which is a read-only operation with no side effects, no data modification, and no execution of external commands. The blast radius is minimal as it only exposes information about recent note modifications.
From the tool's definition Tool name includes 'list' action and description states 'List recently modified notes in TriliumNext' - a query operation that retrieves data without modification.
Attacks that exploit this kind of access
The rule that runs crow_trilium_recent 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_recent, this is the rule to start with:
crow_trilium_recent is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Crow, apply this rule, and every crow_trilium_recent call is checked against it from then on.
Questions about crow_trilium_recent
List recently modified notes in TriliumNext. 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_recent: 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_recent 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_recent 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_recent. 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_recent 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.
This server
Across the catalogue