zk_list_notes_by_date
AI agents call zk_list_notes_by_date to retrieve information from Zettelkasten without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and queries existing notes filtered by date—a read-only operation with no side effects, data modification, or execution risk. Even with the empty description, the naming convention (list + date parameter) strongly indicates a simple query operation. Severity is low because misuse yields only information disclosure, not data loss or harmful execution.
From the tool's definition Tool name 'zk_list_notes_by_date' indicates a retrieval operation that lists or queries notes organized by date. The 'list' verb and temporal filtering suggest data retrieval without modification. Description is empty, lowering confidence slightly.
Attacks that exploit this kind of access
zk_list_notes_by_date. It is categorised as a Read tool in the Zettelkasten MCP Server, which means it retrieves data without modifying state.
Register the Zettelkasten MCP server in PolicyLayer and add a rule for zk_list_notes_by_date: 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 Zettelkasten. Nothing to install.
zk_list_notes_by_date 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 zk_list_notes_by_date 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 zk_list_notes_by_date. 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.
zk_list_notes_by_date is provided by the Zettelkasten MCP server (entanglr/zettelkasten-mcp). 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 →