AI agents call get_note_content 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 tool retrieves note content without modifying or deleting data. The 'get_' prefix and context within a note management system designed for searching and analysis confirm this is a read operation. Confidence is slightly reduced (0.85 rather than higher) because the description is empty, but the name and sibling context provide sufficient evidence.
From the tool's definition Tool name 'get_note_content' and sibling tools 'get_*' patterns (get_last_modified_note, get_linked_by_notes, get_notes, get_random_note, get_related_notes, get_tagless_notes) all indicate retrieval operations.
Attacks that exploit this kind of access
get_note_content. 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_note_content: 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_note_content 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_note_content 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_note_content. 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_note_content 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 →