Retrieve the full note content by note_id or note_tid. Use note_id for unsynced notes, note_tid for synced notes.
AI agents call get_note to retrieve information from Vimango MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves stored note data from a local SQLite database without creating, modifying, deleting, or executing any operations. It has no side effects and poses minimal risk—an AI agent using it could only access existing note content that may already be visible through other means (list_notes, search_notes).
From the tool's definition Tool description states 'Retrieve the full note content by note_id or note_tid.' The verb 'Retrieve' and the lack of any modification, deletion, or execution capabilities indicate this is a read-only operation.
Attacks that exploit this kind of access
Retrieve the full note content by note_id or note_tid. Use note_id for unsynced notes, note_tid for synced notes. It is categorised as a Read tool in the Vimango MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Vimango MCP Server MCP server in PolicyLayer and add a rule for get_note: 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 Vimango MCP Server. Nothing to install.
get_note 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 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. 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 is provided by the Vimango MCP Server MCP server (slzatz/vimango_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 →