retrieve_obsidian_note
AI agents call retrieve_obsidian_note to retrieve information from Obsidian MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Retrieving a note from an Obsidian vault is a read-only operation that queries data without side effects. The name 'retrieve' and the presence of separate write/delete siblings confirm this is data access only. Even if misused by an agent, retrieval poses minimal risk—it cannot modify or destroy data. Severity is low because the blast radius is limited to information disclosure.
From the tool's definition Tool name 'retrieve_obsidian_note' indicates retrieval/querying of note data with no modification. The server description emphasizes 'structured context sources' and 'search', consistent with read operations.
Attacks that exploit this kind of access
retrieve_obsidian_note. It is categorised as a Read tool in the Obsidian MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Obsidian MCP Server MCP server in PolicyLayer and add a rule for retrieve_obsidian_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 MCP Server. Nothing to install.
retrieve_obsidian_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 retrieve_obsidian_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 retrieve_obsidian_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.
retrieve_obsidian_note is provided by the Obsidian MCP Server MCP server (nbaradar/obsidian-mcp-server). 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 →