Identify the most connected notes that serve as knowledge hubs.
AI agents call zk_find_central_notes 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 performs a query or analysis operation to find highly-connected notes based on their link patterns. It has no side effects: it does not create, modify, delete, or execute code. The sibling tools confirm the server's pattern: destructive tools are explicitly named (zk_delete_note), while zk_find_* tools are all read-only discovery operations.
From the tool's definition Tool description states it 'Identify[s] the most connected notes' — a read-only query operation that retrieves data about note connectivity without modifying or deleting any notes.
Documented attack patterns abuse exactly the kind of access zk_find_central_notes gives an agent:
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_find_central_notes:
{
"version": "1",
"default": "deny",
"tools": {
"zk_find_central_notes": {}
}
}zk_find_central_notes 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.
Identify the most connected notes that serve as knowledge hubs. 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_find_central_notes: 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_find_central_notes 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_find_central_notes 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_find_central_notes. 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_find_central_notes 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.
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.