Read a note from the Obsidian vault
AI agents call read_note to retrieve information from Obsidian Nexus without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and queries note content with no side effects or modifications to the vault. It performs a simple read operation consistent with the Read category definition (retrieves or queries data; no side effects). The risk is low because reading existing notes does not alter state or create security obligations, though sensitivity depends on note content (which is outside the tool's control).
From the tool's definition Tool name is 'read_note' and description states 'Read a note from the Obsidian vault'. The verb 'read' and absence of modification language clearly indicate data retrieval only.
Attacks that exploit this kind of access
Read a note from the Obsidian vault. It is categorised as a Read tool in the Obsidian Nexus MCP Server, which means it retrieves data without modifying state.
Register the Obsidian Nexus MCP server in PolicyLayer and add a rule for read_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 Obsidian Nexus. Nothing to install.
read_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 read_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 read_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.
read_note is provided by the Obsidian Nexus MCP server (nkriman/obsidian-nexus). 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 →