AI agents call get_link_to_notes to retrieve information from Zk Utils without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The 'get_' prefix and link-analysis context suggest this tool queries relationships between notes without modifying state. Although the description is empty, the consistent naming pattern with other safe Read operations on this server (get_last_modified_note, get_random_note, get_tagless_notes) and the server's stated purpose of 'note search' and 'link analysis' indicate retrieval rather than modification.
From the tool's definition Tool name 'get_link_to_notes' and server context indicating 'link analysis' capability; no description provided but naming pattern matches other retrieval tools on server (get_notes, get_note_content, get_related_notes).
Attacks that exploit this kind of access
get_link_to_notes. It is categorised as a Read tool in the Zk Utils MCP Server, which means it retrieves data without modifying state.
Register the Zk Utils MCP server in PolicyLayer and add a rule for get_link_to_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 Zk Utils. Nothing to install.
get_link_to_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 get_link_to_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 get_link_to_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.
get_link_to_notes is provided by the Zk Utils MCP server (koei-kaji/zk-utils). 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 →