zk_get_linked_notes
AI agents call zk_get_linked_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 to retrieve or query relationships between notes in a knowledge management system. No side effects, modifications, deletions, or external actions are implied by the name. The 'get_' prefix is typical of Read category operations. Confidence is reduced from 0.95 to 0.85 due to the empty description providing no definitive clarification.
From the tool's definition Tool name 'zk_get_linked_notes' suggests retrieval of linked notes. The empty description limits specificity, but the naming pattern 'get_*' and context within a Zettelkasten note management system indicates a query/retrieval operation with no stated…
Attacks that exploit this kind of access
zk_get_linked_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_get_linked_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_get_linked_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_get_linked_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_get_linked_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_get_linked_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 →