Low Risk

zk_list_notes_by_date

List notes created or modified within a specific date range.

How to control zk_list_notes_by_date ↓

What zk_list_notes_by_date does on Zettelkasten

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.

Low Risk

Why zk_list_notes_by_date needs a policy

This tool retrieves and displays metadata about notes (creation/modification dates) without altering, deleting, or executing any operations. It is a pure read operation that queries the knowledge base. No side effects or data mutations occur. Severity is low because misuse results only in unintended information disclosure from the user's own notes.

From the tool's definition Tool name 'zk_list_notes_by_date' and description 'List notes created or modified within a specific date range' indicate retrieval/querying of existing data with no modification, deletion, or execution of operations.

Documented attack patterns abuse exactly the kind of access zk_list_notes_by_date gives an agent:

How to control zk_list_notes_by_date

PolicyLayer is an MCP gateway — it sits between your AI agents and Zettelkasten, and nothing reaches the server without passing your rules. This is the rule we recommend for zk_list_notes_by_date:

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "zk_list_notes_by_date": {}
  }
}

zk_list_notes_by_date is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.

  1. Create a free account and register Zettelkasten — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
CAP THIS TOOL →

Free to start. No card required.

Related tools and policies

Go deeper

Questions about zk_list_notes_by_date

What does the zk_list_notes_by_date tool do? +

List notes created or modified within a specific date range. It is categorised as a Read tool in the Zettelkasten MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on zk_list_notes_by_date? +

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.

What risk level is zk_list_notes_by_date? +

zk_list_notes_by_date is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit zk_list_notes_by_date? +

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.

How do I block zk_list_notes_by_date completely? +

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.

What MCP server provides zk_list_notes_by_date? +

zk_list_notes_by_date is provided by the Zettelkasten MCP server (liam-deacon/zettelkasten-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Zettelkasten tool call.

Start from Zettelkasten, 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.

14 Zettelkasten tools catalogued and risk-classified — across an index of 43,000+ MCP servers.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.