zk_find_central_notes
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.
The tool appears designed to retrieve or identify central/hub notes in the knowledge graph—a read-only query operation with no side effects on data. While the empty description reduces confidence slightly, the naming convention and context of sibling tools strongly indicate this is a discovery/search function rather than a modification or destructive operation.
From the tool's definition Tool name 'zk_find_central_notes' suggests a search/query operation within the Zettelkasten knowledge base.
Attacks that exploit this kind of access
zk_find_central_notes. 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 (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 →